AI Agent Workflow Collection

Decompose a technical design document into a DAG (directed acyclic graph) of work tasks. Use this skill whenever the user asks to "break down" / "decompose" / "split up" a design into tasks, create a task DAG, sequence the work, or build a task list with dependencies. Trigger on phrases like "decompose the design at ... into tasks", "break this design into a task DAG", "create the task list with dependencies", "what's the work breakdown for this design", "sequence the tasks for ...", "decompose into a DAG", "build the work plan for the design". This is the step after a technical design — it produces a human-reviewable DAG (index.md with Mermaid + table) plus skeleton task files (one per task, with frontmatter), which the task-specs skill later fleshes out into full per-task specs.

Generate a technical design document as a markdown file, given a PRD (or PRD-shaped description). Use this skill whenever the user asks for a tech design, technical design doc, architecture doc, implementation design, engineering design, RFC, or wants to "design the implementation of" / "figure out how we'd build" / "spec out the architecture for" a feature. Trigger on phrases like "write a tech design for the PRD at ...", "design the implementation of X", "how would we architect this", "turn this PRD into a design". This is the step after a PRD — it converts product intent into engineering specifics (components with real file paths, data model, API contracts, existing patterns to reuse). It is not the right fit for product/requirements docs (use prd-generator) or for breaking work into tasks (use task-dag).