speckit-tasks.agent

Generating executable task plans from user stories involves reading spec.md and plan.md to extract feature names and priorities, then producing a dependency graph. This approach organizes tasks into phased milestones like Setup, Foundational, and Polish, ensuring correct execution order for feature implementation.

Generating a phased milestone task plan from spec.md involves extracting feature names, tech stack, and user stories, then grouping tasks into Setup, Foundational, US, and Polish phases. This creates a dependency graph ensuring correct execution order for feature implementation.

Yes, you can use existing data models and contracts when generating a tasks.md plan. The process reads optional documents including data-model.md, contracts/, research.md, and quickstart.md alongside plan.md and spec.md to assemble comprehensive, dependency-aware tasks organized by user stories.

Yes, you need a SPEC-KIT project structure with a .specify/ directory to generate a dependency-aware tasks.md. The system requires plan.md and spec.md placed in the feature directory to extract user stories and enforce strict task formatting rules for feature implementation.

Task generation rules for an executable tasks.md file enforce strict formatting, testability, and dependency-awareness to produce a complete plan. The output includes the generated file path, task counts, parallel opportunities, and MVP scope to guide feature implementation.