task-create

Task creation generates numbered Markdown files in docs/planning/tasks/ with standardized sections including Goal, Context, Plan, Acceptance Criteria, Test Plan, Scope, and Notes. Run aaa task create <kebab-name> to automatically populate a templated file, optionally linking a Story, ensuring consistent documentation across your development work.

Automated task templates include Goal, Context, Plan, Acceptance Criteria, Test Plan, Scope, and Notes sections. This structure captures essential planning information—why the task exists, what preconditions apply, how to execute it, what success looks like, and any constraints—eliminating gaps in unstructured documentation.

Yes, the aaa task create command supports optional Story links within the template. This integration ties task documentation to broader project narratives, maintaining traceability between detailed execution plans and higher-level project goals or feature requests.

Structured templates enforce consistent formatting and required sections across all task files. By using automated task creation instead of manual documentation, your team generates uniform task records in docs/planning/tasks/ with predictable structure, reducing ambiguity and improving onboarding clarity.

Numbered Markdown files in a centralized planning directory provide sequential, searchable task organization. Templated structure ensures each task captures goals and acceptance criteria upfront, enabling better prioritization, delegation, and progress tracking compared to scattered notes or informal checklists.

No prerequisites are required; task templates are self-contained and generate from scratch using the aaa binary directly. The command outputs a populated file path immediately, making it suitable for new projects or existing workflows regardless of current documentation depth.