task-planning

To generate a TASK.md skeleton, provide your epic and user story context to automatically produce a template with metadata, acceptance criteria, and TDD placeholders. This ensures immediate traceability and structured task documentation without manual formatting.

An auto-generated task template includes standardized metadata fields for Priority, Status, Estimate, and Assignee. It also enforces placeholders for implementation steps and acceptance criteria to ensure comprehensive task tracking.

Task planning links technical tasks to project epics by embedding epic and user story references directly into the TASK.md document. This preserves alignment with overarching project goals and maintains clear hierarchical traceability.

You do not need to manually format acceptance criteria. The task template auto-generates dedicated sections for acceptance criteria and TDD step placeholders, eliminating the manual drafting burden for engineering tasks.

You can use this approach for test-driven development workflows because the generated TASK.md includes specific placeholders for TDD steps. This integrates seamlessly into TDD processes by providing ready-to-use structural steps.

The best way to standardize engineering task documentation is enforcing a uniform TASK.md template with metadata, acceptance criteria, and traceability links. This ensures all team members follow consistent task structures and project alignment.