Task prd creator
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.
npx -y skills add coco-research/coco --skill task-prd-creatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.4 KB, as published. Nobody here has run it
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
- Create task file
- Create PRD file
- Link them together
- Present to user
- Get approval
- Then implement
Red Flags (Stop and Ask)
- Breaking changes
- Affects multiple projects
- Security implications
- Unclear requirements
Integration
mvp-architect- MVP scopingplanning-assistant- Content planningagent-folder-init- Initialize .agent/ structure
For complete PRD template, naming conventions, status update workflow, Context7 integration, and example interactions, see: references/full-guide.md