speckit-tasks

Generating dependency-ordered tasks from a specification requires reading design artifacts like plan.md and spec.md to produce an actionable tasks.md checklist. The process builds setup, foundational, and user-story phases with explicit completion ordering.

Structuring a feature implementation checklist from plan and spec files involves parsing design documents into a strict checklist format with task IDs, story labels, file paths, and dependencies. This ensures teams can execute and validate work without guessing execution order.

The task generator does support workflow hooks by discovering and rendering before/after extension hooks from a .specify/extensions.yml file. It respects enabled and optional flags while rendering tasks, without evaluating the underlying hook conditions.

You can include data models and interface contracts when generating project scaffolding tasks by providing optional design documents. The generator enriches the task checklist using data-model.md, contracts/, research.md, and quickstart.md files when they are present in the feature directory.

Creating parallel execution opportunities in a generated task checklist happens automatically when the generator analyzes the dependency graph of your design artifacts. It marks independent tasks with optional parallel markers so teams can execute concurrent work safely.

Before generating tasks for feature planning, you must prepare a required plan.md and spec.md file within your spec-kit project structure. Optionally, you can also include data-model.md, research.md, and quickstart.md to enrich the output.