task-create
Create structured task files for planning dev work. Use when user asks to "create a task", "add a task", "plan a task", or needs to document work items. Creates numbered markdown files in docs/planning/tasks/.
When & Why to Use This Skill
This Claude skill automates the creation of structured markdown task files to streamline development planning and documentation. By generating standardized templates that include goals, context, action plans, and acceptance criteria, it ensures consistent project tracking and improves workflow transparency within engineering teams.
Use Cases
- Technical Task Planning: Use this skill to quickly generate a comprehensive task file when starting a new feature, ensuring all technical requirements and dependencies are documented.
- Workflow Standardization: Enforce project conventions by automatically creating numbered markdown files in a centralized planning directory with predefined headers like 'Scope' and 'Test Plan'.
- Task Decomposition: Efficiently break down complex user stories into smaller, actionable work items with clear 'In' and 'Out' boundaries to prevent scope creep.
- Asynchronous Collaboration: Maintain a clear, version-controlled history of planned work within the codebase to improve team alignment and knowledge sharing.
| name | task-create |
|---|---|
| description | Create structured task files for planning dev work. Use when user asks to "create a task", "add a task", "plan a task", or needs to document work items. Creates numbered markdown files in docs/planning/tasks/. |
Task Create
Create numbered task files following project conventions.
Workflow
IMPORTANT: Use the aaa binary directly, NOT bun --cwd tools run dev.
- Create file:
aaa task create <kebab-name>→ returns filepath - Write content using template below
- Link to story if applicable (add
**Story:**header)
Template
## Task: [Short descriptive name]
**Story:** [story-name](../stories/NNN-story-name.md) *(optional)*
### Goal
[One sentence: what should be true when this is done?]
### Context
[Why this matters. Current state, trigger, constraints, dependencies]
### Plan
1. [First concrete action]
2. [Second action]
3. [Continue as needed]
### Acceptance Criteria
- [ ] [Specific, testable outcome]
- [ ] [Another outcome]
### Test Plan
- [ ] [What tests to add/run]
- [ ] [Manual verification if needed]
### Scope
- **In:** [What this includes]
- **Out:** [What this explicitly excludes]
### Notes
[Optional: Technical considerations, risks, edge cases]
Required Sections
| Section | Purpose |
|---|---|
| Goal | One sentence outcome - "what's true when done?" |
| Context | The why: problem, trigger, constraints |
| Plan | Numbered concrete actions |
| Acceptance Criteria | Checkboxes for verification |
| Test Plan | What tests to add/update/run |
| Scope | Explicit In/Out boundaries |
File Location
- Default:
docs/planning/tasks/NNN-name.md - Custom:
aaa task create <name> --dir <path>