From claude-commands
Generates actionable, dependency-ordered tasks.md for a feature from design artifacts (plan.md, data-model.md, contracts), with parallel markers [P] and execution guidance.
npx claudepluginhub jleechanorg/claude-commandscommands/spec-kit/## ⚡ EXECUTION INSTRUCTIONS FOR CLAUDE
**When this command is invoked, YOU (Claude) must execute these steps immediately:**
**This is NOT documentation - these are COMMANDS to execute right now.**
**Use TodoWrite to track progress through multi-phase workflows.**
## 🚨 EXECUTION WORKFLOW
### Phase 1: Execute Documented Workflow
**Action Steps:**
The user input to you can be provided directly by the agent or as a command argument - you **MUST** consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and...When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.
Action Steps: The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
Run {SCRIPT} from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.
Load and analyze available design documents:
Note: Not all projects have all documents. For example:
Generate tasks following the template:
/templates/tasks-template.md as the baseTask generation rules:
Order tasks by dependencies:
Include parallel execution examples:
Create FEATURE_DIR/tasks.md with:
Context for task generation: {ARGS}
The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.
The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
$ARGUMENTS
Run {SCRIPT} from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.
Load and analyze available design documents:
Note: Not all projects have all documents. For example:
Generate tasks following the template:
/templates/tasks-template.md as the baseTask generation rules:
Order tasks by dependencies:
Include parallel execution examples:
Create FEATURE_DIR/tasks.md with:
Context for task generation: {ARGS}
The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.