Break down a completed SPEC into AI-structured TODO tasks with dependencies.
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-tasks
Please help me install this Agent Skill. Skill: doc-tasks Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-tasks Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-tasks
This Skill creates a Task Breakdown (TASKS) artifact—Layer 11—that decomposes a completed SPEC into AI-structured, executable tasks for implementation planning and execution.
Provide the Layer 10 SPEC (SPEC) and request a TASKS breakdown. The output will be a structured, phase-based list of tasks ready for IPLAN and execution planning.
High-intent search queries and answers about installing and using this skill.
Task breakdown decomposes a completed SPEC into AI-structured, executable tasks organized by phase. Provide your Layer 10 SPEC and receive a TASKS artifact with task IDs, titles, actions, file targets, dependencies, effort estimates, and success criteria ready for implementation planning.
Traceability links each task back to upstream artifacts—BRD, PRD, EARS, or SPEC—creating an end-to-end audit trail. Task breakdown maintains this chain by referencing the source SPEC in every task, ensuring accountability and enabling impact analysis across the development workflow.
Yes. Task breakdown generates phase-driven task hierarchies compatible with both AI-agent-based and traditional 8-layer architectures. Output feeds directly into Phase 12 IPLAN and Phase 13 Code execution, supporting autonomous or human-managed implementation.
Task breakdown produces a structured TASKS artifact containing task IDs (TASK-{SPEC-ID}-{N}), titles, actions, files to create or modify, task dependencies, effort estimates, SPEC references, success criteria, and a Mermaid dependency diagram for visual planning.
Phase-driven planning organizes tasks into a clear hierarchy aligned to the SDD workflow, reducing scope ambiguity and enabling parallel execution tracking. Task breakdown structures output by phase so teams know execution sequence, blockers, and completion milestones upfront.
Yes. Task breakdown requires a completed Layer 10 SPEC as input. The SPEC must be finalized so tasks reflect all requirements, constraints, and architectural decisions without requiring rework during execution.
vladm3105Convert completed SDD artifacts into machine-readable SPEC YAML documents.
filimorniga-uxConvert ideas into phased project plans with tasks, timelines, risks, and deliverables.
vladm3105Create formal EARS Layer 3 requirements documents using WHEN-THE-SHALL-WITHIN syntax.
insentekOrchestrate approved software proposals with multi-agent task decomposition and audit gates.
