This skill should be used when the user asks to "analyze a specification", "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 comprehensive guidance for transforming specifications into structured, actionable task lists optimized for AI coding agents.
View on GitHubJanuary 25, 2026
Select agents to install to:
npx add-skill https://github.com/sequenzia/claude-plugins/blob/main/plugins/task-manager/skills/spec-task-management/SKILL.md -a claude-code --skill spec-task-managementInstallation paths:
.claude/skills/spec-task-management/# Spec Task Management Transform specification documents (PRDs, Technical Specifications, Design Documents) into structured task lists that AI coding agents can execute independently or in parallel. ## Core Workflow ### 1. Document Analysis Parse the specification document to extract: - **Explicit requirements**: Stated features, functionality, acceptance criteria - **Implicit requirements**: Technical considerations, infrastructure needs, error handling - **Constraints**: Technology choices, performance requirements, compatibility needs - **Scope boundaries**: What is and isn't included in the specification Read the source document thoroughly. Identify section headings, numbered requirements, user stories, acceptance criteria, and technical specifications. Note any cross-references between sections. ### 2. Task Decomposition 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 by different agents without coordination | | Clear boundaries | Well-defined start and end conditions | | Testable | Verifiable completion criteria exist | **Decomposition process:** 1. Identify each distinct requirement in the specification 2. Determine if the requirement is atomic or needs splitting 3. Create task entries with unique IDs (TASK-001, TASK-002, etc.) 4. Ensure each task maps to specific specification sections ### 3. Dependency Mapping Identify three types of dependencies between tasks: - **Hard dependencies**: Task B cannot start until Task A completes - **Soft dependencies**: Task B benefits from Task A being complete but can proceed - **Resource dependencies**: Tasks share files, modules, or services Populate `dependencies.hard` and `dependencies.soft` arrays. Calculate `blocked_by` (incomplete hard dependencies) and `blocks` (tasks depending on this one). For d