/speckit-tasks

name: "speckit-tasks"
description: "Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts."
argument-hint: "Optional task generation constraints"
compatibility: "Requires spec-kit project structure with .specify/ directory"
metadata:
  author: "github-spec-kit"
  source: "templates/commands/tasks.md"
user-invocable: true
disable-model-invocation: false

User Input

$ARGUMENTS

You **MUST** consider the user input before proceeding (if not empty).

Pre-Execution Checks

**Check for extension hooks (before tasks generation)**:

• Check if `.specify/extensions.yml` exists in the project root.
• If it exists, read it and look for entries under the `hooks.before_tasks` key
• If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
• Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
• For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
• If the hook has no `condition` field, or it is null/empty, treat the hook as executable
• If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
• When constructing command invocations from hook command names, replace dots (`.`) with hyphens (`-`). For example, `speckit.git.commit` → `/speckit-git-commit`.
• For each executable hook, output the following based on its `optional` flag:
• **Optional hook** (`optional: true`):

    ## Extension Hooks

    **Optional Pre-Hook**: {extension}
    Command: `/{command}`
    Description: {description}

    Prompt: {prompt}
    To execute: `/{command}`

• **Mandatory hook** (`optional: false`):

    ## Extension Hooks

    **Automatic Pre-Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}

    Wait for the result of the hook command before proceeding to the Outline.

After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal `{command}` id shown above, e.g. a skills-mode agent runs it as `/skill:speckit-...` or `$speckit-...`). Emitting the block alone does not run the hook.

• If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

Outline

1. **Setup**: Run `.specify/scripts/bash/setup-tasks.sh --json` from repo root and parse FEATURE_DIR, TASKS_TEMPLATE_CONTENT, TASKS_TEMPLATE, and AVAILABLE_DOCS list. `FEATURE_DIR` and `TASKS_TEMPLATE` must be absolute paths when provided. `AVAILABLE_DOCS` is a list of document names/relative paths available under `FEATURE_DIR` (for example `research.md` or `contracts/`). For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").

2. **Load design documents**: Read from FEATURE_DIR:

• **Required**: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
• **Optional**: data-model.md (entities), contracts/ (interface contracts), research.md (decisions), quickstart.md (test scenarios)
• **IF EXISTS**: Load `.specify/memory/constitution.md` for project principles and governance constraints
• Note: Not all projects have all documents. Generate tasks based on what's available.

3. **Execute task generation workflow**:

• Load plan.md and extract tech stack, libraries, project structure
• Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
• If data-model.md exists: Extract entities and map to user stories
• If contracts/ exists: Map interface contracts to user stories
• If research.md exists: Extract decisions for setup tasks
• Generate tasks organized by user story (see Task Generation Rules below)
• Generate dependency graph showing user story completion order
• Create parallel execution examples per user story
• Validate task completeness (each user story has all needed tasks, independently testable)

4. **Generate tasks.md**: Use TASKS_TEMPLATE_CONTENT (from the JSON output above) as the structure. For compatibility with older setup scripts that omit TASKS_TEMPLATE_CONTENT, read TASKS_TEMPLATE instead. Fill with:

• Correct feature name from plan.md
• Phase 1: Setup tasks (project initialization)
• Phase 2: Foundational tasks (blocking prerequisites for all user stories)
• Phase 3+: One phase per user story (in priority order from spec.md)
• Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
• Final Phase: Polish & cross-cutting concerns
• All tasks must follow the strict checklist format (see Task Generation Rules below)
• Clear file paths for each task
• Dependencies section showing story completion order
• Parallel execution examples per story
• Implementation strategy section (MVP first, incremental delivery)

Mandatory Post-Execution Hooks

**You MUST complete this section before reporting completion to the user.**

Check if `.specify/extensions.yml` exists in the project root.

• If it does not exist, or no hooks are registered under `hooks.after_tasks`, skip to the Completion Report.
• If it exists, read it and look for entries under the `hooks.after_tasks` key.
• If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue to the Completion Report.
• Filter out hooks where `ena