Convert approved software specs into ordered implementation plans with verification commands.
npx skills add https://github.com/nuttaruj/rolepod --skill write-plan-nuttaruj
Please help me install this Agent Skill. Skill: write-plan Source: https://github.com/nuttaruj/rolepod/tree/main/core/skills/write-plan Command: npx skills add https://github.com/nuttaruj/rolepod --skill write-plan-nuttaruj
This Skill helps teams avoid jumping into implementation with vague or incomplete plans. It turns an approved spec or a clear engineering goal into a concrete execution artifact with ordered tasks, exact files to touch, verification commands, ownership, and failure handling before any code is edited.
Ask the AI to use write-plan to turn your approved spec into an ordered implementation plan with exact files, per-task tests, owners, and runnable verification commands.
High-intent search queries and answers about installing and using this skill.
Implementation planning converts an approved spec into ordered tasks with exact file paths, per-task test evidence, ownership, and runnable verification commands. It defines sequencing, routing, and failure policies before code editing begins.
Parallel agent coordination uses cohesion contracts to define ownership, shared interfaces, and merge order across multiple sessions. This ensures multiple agents can work on multi-file features simultaneously without conflicting edits or breaking shared symbols.
Generating a build plan requires an approved software spec or clear engineering goal, explicit file paths, and defined test evidence. You also need per-task verification commands and failure policies for high-risk changes like API, migration, auth, or billing work.
Task sequencing for a multi-file refactor requires ordering tasks by dependency, assigning exact file ownership, and defining completion criteria and runnable verification commands. Spec coverage tracing and anti-placeholder rules ensure each step maintains symbol consistency.
Spec coverage tracing and cohesion contracts are needed when planning multi-owner parallel work or high-risk changes. They ensure every spec requirement maps to a task and shared interfaces remain stable across concurrent agents or sessions.
heymishyDefine completion criteria requiring implementation, test, and changelog files for feature development.
shichengwuyuRun full verification commands and attach output evidence before marking work complete.
drvossEnforce failing tests before implementation to drive Test-Driven Development workflows.
dreamingechoesDraft structured project specs covering requirements, design, testing, and acceptance criteria.
