Convert accepted designs into ordered implementation plans with acceptance criteria and file changes.
npx skills add https://github.com/usurobor/cnos --skill plan-usurobor
Please help me install this Agent Skill. Skill: plan Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/plan Command: npx skills add https://github.com/usurobor/cnos --skill plan-usurobor
Converts an accepted design into a concrete, ordered plan that specifies per-step acceptance criteria and the exact files to modify for execution.
Describe an accepted design artifact and let this skill generate an ordered implementation sequence with per-step acceptance criteria and file-change specifications.
High-intent search queries and answers about installing and using this skill.
To turn an accepted design into an implementation plan, you provide the design artifact and generate an ordered sequence with per-step acceptance criteria and explicit file changes. This ensures traceable and reproducible execution of complex workflows.
Design-to-implementation traceability in project planning maps abstract design artifacts to concrete execution steps. It documents required dependencies, per-step file changes, and acceptance criteria to ensure deterministic execution and verifiable outcomes.
You generate per-step acceptance criteria for engineering workflows by processing an accepted design artifact. The resulting ordered implementation sequence specifies verifiable outcomes and explicit file modifications required for each milestone.
Yes, you can use an implementation plan to specify exact file changes for operators. The plan includes a clear change map and dependency awareness, guiding engineers through implementation milestones with reproducible execution.
Yes, you need an accepted design artifact before creating an implementation sequence. The skill transforms an accepted design into an ordered plan, meaning a finalized design input is a prerequisite for generating the step-level execution guide.
The best way to manage artifact dependencies in a project plan is by generating an ordered implementation sequence that documents required dependencies and per-step file changes, ensuring traceable execution and clearly labeled plan boundaries.
OzeroHAXDefine project context, problem statement, and MVP boundaries.
mortenbroesbyBreak down complex requests into ordered, verifiable slices with acceptance criteria.
UnicornBreak down project requirements into structured iterations and tasks with dependencies and acceptance criteria.
FrogAiGenerate executable plans with explicit commands, files, and verification steps.
