2.3 KiB
TASK-{ID}: {Title}
Template: Feature Created: YYYY-MM-DD Last Updated: YYYY-MM-DD
Status
| Field | Value |
|---|---|
| State | pending |
| Priority | P{0-3} |
| Cell | {backend / frontend / ux_ui} |
| Assigned To | {agent-id or "unassigned"} |
| Created By | {agent-id} |
| Initiative | {initiative-id or "standalone"} |
Timeline
| Milestone | Date |
|---|---|
| Created | YYYY-MM-DD |
| Claimed | - |
| Started | - |
| QA Submitted | - |
| QA Passed | - |
| Docs Complete | - |
| Completed | - |
Overview
{2-3 sentence description of what this feature is and why it's needed}
User Story
As a {type of user} I want {capability} So that {benefit}
Context
{Why is this being built now? What's the business driver? Any relevant background.}
Acceptance Criteria
- {Criterion 1 - specific, testable}
- {Criterion 2 - specific, testable}
- {Criterion 3 - specific, testable}
- {Criterion 4 - specific, testable}
Out of Scope
- {What is explicitly NOT included in this task}
- {Helps prevent scope creep}
Technical Details
Approach
{High-level technical approach - filled in during planning phase}
Key Files
{Primary files that will be created/modified}
path/to/file1path/to/file2
Dependencies
- Blocked by: {TASK-XXX or "none"}
- Blocks: {TASK-XXX or "none"}
- Related: {TASK-XXX or "none"}
API Changes
{If applicable: new endpoints, changed contracts}
Database Changes
{If applicable: new tables, migrations}
Design Assets
{For frontend/UX tasks - links to designs}
- Figma: {link or "N/A"}
- Prototype: {link or "N/A"}
- States Covered: {list or "N/A"}
Commits
| Commit | Description | Date |
|---|---|---|
| - | No commits yet | - |
Quick Context Restore
{2-3 sentences that let any agent quickly understand where this task stands. Update this whenever you pause work.}
Current state: Not started Next action: Claim and begin planning Blockers: None
Notes
{Any additional context, links, references, or considerations}
Changelog
| Date | Agent | Change |
|---|---|---|
| YYYY-MM-DD | {agent} | Task created |