/task-prd-creator
Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan
$ npx -y skills add coco-research/coco --skill task-prd-creator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/task-prd-creator
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan
SKILL.md
task-prd-creator.SKILL.mdname: task-prd-creator
description: Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan this feature", or any feature request.
version: 1.0.0
tags:
- planning
- task-management
- prd
- workflow
- documentation
- project-management
auto_activate: true
domain: pm
Task & PRD Creator
Overview
Create structured task files and PRDs before implementing features. This ensures proper planning, documentation, and clear scope definition.
**CRITICAL RULE:** Never implement a feature without first creating the task + PRD files and getting user approval.
When This Activates
- "I want to add [feature]"
- "Implement [feature]"
- "Create a task for [feature]"
- "Plan this feature"
- User describes a user story
- Bug that needs tracking
The Workflow
Step 1: Understand Request
- **Simple task:** <1 hour, few files
- **Complex feature:** >1 hour, multiple files/systems
Step 2: Gather Requirements
- Which app/project?
- Priority? (CRITICAL/High/Medium/Low)
- Dependencies?
Step 3: Check Existing System
- Read architecture docs
- Search for similar implementations
Step 4: Create Files
**Task file:** `[project]/.agent/TASKS/[task-name].md` **PRD file:** `[project]/.agent/PRDS/[task-name].md`
Step 5: Get Approval
Present files, explain approach, **WAIT for user approval**.
Task File Format
## Task: [Feature Name]
**ID:** feature-name-slug
**Label:** [App]: [Feature Name]
**Description:** Brief description
**Type:** Feature | Bug | Enhancement
**Status:** Backlog | To Do | Testing | Done
**Priority:** High | Medium | Low
**Created:** YYYY-MM-DD
**Updated:** YYYY-MM-DD
**PRD:** [Link](../PRDS/feature-name.md)
Critical Rules
1. Create task file 2. Create PRD file 3. Link them together 4. Present to user 5. Get approval 6. Then implement
Red Flags (Stop and Ask)
- Breaking changes
- Affects multiple projects
- Security implications
- Unclear requirements
Integration
- `mvp-architect` - MVP scoping
- `planning-assistant` - Content planning
- `agent-folder-init` - Initialize .agent/ structure
---
**For complete PRD template, naming conventions, status update workflow, Context7 integration, and example interactions, see:** `references/full-guide.md`
Read more
name: task-prd-creator description: Use this skill when users request new features, enhancements, bug fixes, or any work that needs planning. Creates structured task files and PRDs (Product Requirements Documents) before implementation. Activates for "I want to add X", "implement Y", "create a task for Z", "plan this feature", or any feature request. version: 1.0.0 tags: - planning - task-management - prd - workflow - documentation - project-management auto_activate: true domain: pm
Task & PRD Creator
Overview
Create structured task files and PRDs before implementing features. This ensures proper planning, documentation, and clear scope definition.
**CRITICAL RULE:** Never implement a feature without first creating the task + PRD files and getting user approval.
When This Activates
- "I want to add [feature]"
- "Implement [feature]"
- "Create a task for [feature]"
- "Plan this feature"
- User describes a user story
- Bug that needs tracking
The Workflow
Step 1: Understand Request
- **Simple task:** <1 hour, few files
- **Complex feature:** >1 hour, multiple files/systems
Step 2: Gather Requirements
- Which app/project?
- Priority? (CRITICAL/High/Medium/Low)
- Dependencies?
Step 3: Check Existing System
- Read architecture docs
- Search for similar implementations
Step 4: Create Files
**Task file:** `[project]/.agent/TASKS/[task-name].md` **PRD file:** `[project]/.agent/PRDS/[task-name].md`
Step 5: Get Approval
Present files, explain approach, **WAIT for user approval**.
Task File Format
## Task: [Feature Name] **ID:** feature-name-slug **Label:** [App]: [Feature Name] **Description:** Brief description **Type:** Feature | Bug | Enhancement **Status:** Backlog | To Do | Testing | Done **Priority:** High | Medium | Low **Created:** YYYY-MM-DD **Updated:** YYYY-MM-DD **PRD:** [Link](../PRDS/feature-name.md)
Critical Rules
1. Create task file 2. Create PRD file 3. Link them together 4. Present to user 5. Get approval 6. Then implement
Red Flags (Stop and Ask)
- Breaking changes
- Affects multiple projects
- Security implications
- Unclear requirements
Integration
- `mvp-architect` - MVP scoping
- `planning-assistant` - Content planning
- `agent-folder-init` - Initialize .agent/ structure
---
**For complete PRD template, naming conventions, status update workflow, Context7 integration, and example interactions, see:** `references/full-guide.md`
Meet Coco. A superintelligent agent framework powered by an advisory board of 389 world-class minds. Scale your AI assistant into a complete engineering department with 142 skills, 277 commands, and persistent state. Universal compatibility. Local privacy. Free and open source.
Repo: coco-research/coco
Other skills on coco.
- /create-rule
Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or AGENTS.md.
Open skill - /create-skill
Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
Open skill - /create-subagent
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
Open skill - /migrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when the user wants to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands
Open skill - /update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Open skill - /agent-lightning
Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent training, instrumenting agents with tracing, configuring LightningStore, implementing reward functions, or optimizing prompts with RL/APO algorithms.
Open skill

