speckit-tasks

To break down a project plan into actionable tasks, load plan.md and spec.md from a feature directory to map user stories into a phase-based tasks.md file with dependency graphs and parallel execution examples.

Generating a dependency graph for user stories involves analyzing spec.md and plan.md to sequence tasks into Phase 1 Setup, Phase 2 Foundational, and Phase 3+ phases, outputting a strict checklist format with execution order.

Converting a feature spec into a task checklist requires parsing spec.md alongside plan.md to produce a tasks.md file, enforcing a strict checklist format for every task and mapping them to prioritized user stories.

Yes, you can include optional sources like data-model.md, contracts/, and research/ directories when generating task lists to enrich the context for mapping implementation tasks to user stories.

Yes, the generated task list provides MVP recommendations by reporting a summary that includes total tasks, per-story counts, and prioritized phases to guide the minimum viable product development.

Mapping tasks to user stories requires markdown files, specifically plan.md and spec.md within a feature folder, which are analyzed to output a structured tasks.md file with dependency-aware sequencing.