Create atomic implementation plans with dependency graphs from design discussions.
npx skills add https://github.com/steven-3/supermind --skill writing-plans-steven-3
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/steven-3/supermind/tree/main/skills/writing-plans Command: npx skills add https://github.com/steven-3/supermind --skill writing-plans-steven-3
It prevents execution failures caused by vague requirements by turning a design discussion into granular, atomic, dependency-ordered implementation plans that an executor can complete with fresh context.
Use the orchestrator Plan phase so writing-plans generates implementation tasks and saves them under the appropriate phase planning directories.
High-intent search queries and answers about installing and using this skill.
Implementation planning breaks designs into self-contained, dependency-ordered tasks that parallel executors can safely complete in waves. Each task specifies exact files to read or modify, ensuring reliable execution with fresh context.
Implementation planning generates task graphs by reading design discussions and outputting per-task specs with dependencies, acceptance criteria, and verification commands. This prevents execution failures caused by vague requirements and context loss between executors.
Implementation planning injects methodology by task type, aligning bug fixes with the REPRODUCE-ISOLATE-FIX-VERIFY approach. It creates granular tasks with concrete verification steps, ensuring each fix is isolated, testable, and verifiable within a fresh context window.
Implementation planning aligns feature and test tasks with Test-Driven Development methodology. It decomposes work into 2-5 minute atomic tasks, each with explicit acceptance criteria and verification commands, enforcing no-placeholder rules for reliable TDD execution.
Implementation planning applies to product changes, bug fixes, refactors, and test writing. It specifies exact file-level instructions and dependency ordering, allowing executors to safely refactor code with fresh context while maintaining verification integrity.
Orchestration execution fails when tasks lack explicit file-level guidance and verification steps. Implementation planning prevents this by enforcing no-placeholder rules, dependency graphs, and per-task acceptance criteria, ensuring each executor completes work in 2-5 minutes reliably.
TK-Evans01Orchestrate a six-phase design planning workflow with task tracking.
MajesteitBartBreak approved plans into atomic tasks with dependencies and acceptance criteria.
am-willOrchestrate parallel subagents to execute development plan tasks in waves.
zli5460Decompose project plans into routed Kanban tasks with dependencies.
