From mission-control
This skill should be used when the user asks to "generate tasks from a spec", "break down a spec", "create tasks from a PRD", "decompose requirements", "generate a task list from a design document", or mentions working from specification documents. Provides guidance for transforming specifications into structured, actionable task lists organized under missions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mission-control:skills/simple-task-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform specification documents (PRDs, Technical Specifications, Design Documents) into structured task lists organized under named missions that can be executed systematically.
Transform specification documents (PRDs, Technical Specifications, Design Documents) into structured task lists organized under named missions that can be executed systematically.
Parse the specification document to extract:
Read the source document thoroughly. Identify section headings, numbered requirements, user stories, acceptance criteria, and technical specifications. Note any cross-references between sections.
Break requirements into atomic tasks with these characteristics:
| Characteristic | Description |
|---|---|
| Single responsibility | Each task addresses one specific piece of functionality |
| Independence | Tasks can be worked on without coordination where possible |
| Clear boundaries | Well-defined start and end conditions |
| Testable | Verifiable completion criteria exist |
Decomposition process:
Identify blocking dependencies between tasks:
Populate the dependencies array with task IDs this task depends on. Calculate blocked_by (incomplete dependencies) and blocks (tasks depending on this one).
Score and prioritize tasks based on:
Map to priority levels: critical, high, medium, low.
PRD Priority Mapping:
For each task, generate acceptance criteria:
Group tasks into phases based on dependency analysis:
Generate task lists as JSON following the schema in references/task-schema.json.
Key structure:
{
"mission": {
"name": "Build User Authentication System",
"metadata": {
"source_document": "path/to/spec.md",
"generated_at": "2024-01-15T10:30:00Z",
"last_updated": "2024-01-15T10:30:00Z",
"version": "1.0.0",
"total_tasks": 12,
"completion_percentage": 0
},
"tasks": [...],
"execution_phases": [...]
}
}
Store task files at: missions/<mission-slug>/<project-name>.tasks.json
The mission slug is derived from the mission name:
Example: "Build User Authentication" → missions/build-user-authentication/
Create the missions/<mission-slug>/ directory if it doesn't exist. Use the specification filename (without extension) as the project name, or derive from specification title.
Maintain version history by incrementing mission.metadata.version on updates.
Track task lifecycle:
| Status | Description |
|---|---|
| not_started | Task not yet begun |
| in_progress | Currently being worked on |
| blocked | Cannot proceed due to incomplete dependencies |
| complete | Task finished and verified |
When marking a task complete:
blocked_by for all dependent taskscompletion_percentage in metadataUse T-shirt sizing with these guidelines:
| Size | Typical Scope |
|---|---|
| XS | Single function, simple change, < 20 lines |
| S | Single file, straightforward logic, 20-100 lines |
| M | Multiple files, moderate complexity, 100-300 lines |
| L | Multiple components, significant logic, 300-800 lines |
| XL | System-wide, complex integration, > 800 lines |
When specifications are unclear:
notes fieldGenerate command flow:
missions/<mission-slug>/<project-name>.tasks.jsonNext task selection criteria:
For the task list schema, consult:
references/task-schema.json - JSON schema for task list formatnpx claudepluginhub sequenzia/claude-plugins --plugin mission-controlGenerates parallelizable, atomic task lists from approved specs with dependencies and priorities. Groups tasks into sessions and tracks progress.
Decomposes specs into one-file-per-task under tasks/ with dependency graphs and parallel lane suggestions. Activates when specs/ has unmapped specs or user mentions task decomposition.
Breaks PRDs into ordered production-ready engineering tasks with embedded success criteria, tests, benchmarks, and non-functional requirements for /execute-task execution. Use for PRD-to-tasks conversion and feature planning as mergeable PRs.