Generate a reviewable code change plan through structured Clarify, Approach, and Summary stages.
npx skills add https://github.com/rupertsworld/skills --skill code-plan-rupertsworld
Please help me install this Agent Skill. Skill: code-plan Source: https://github.com/rupertsworld/skills/tree/main/code-plan Command: npx skills add https://github.com/rupertsworld/skills --skill code-plan-rupertsworld
Planning code changes is often ambiguous and risk-prone. This skill provides a guided, multi-stage dialogue to clarify goals, constraints, and acceptance criteria, producing a clear, auditable plan before any implementation.
Start a planning session by triggering the Clarify stage and guiding the user through Approach and Summary report before drafting the plan.
High-intent search queries and answers about installing and using this skill.
To create a formal plan for code changes, use a structured multi-stage dialogue that cycles through Clarify, Approach, and Summary stages. This process captures goals, constraints, and acceptance criteria to produce a reviewable plan ready for stakeholders.
Documenting architecture and acceptance criteria is best handled through a guided Q&A flow that captures decisions stage-by-stage. This generates a concise, shareable summary report aligning engineers and stakeholders before any code is written.
Structured Q&A helps plan code changes by guiding users through a multi-stage dialogue that explicitly surfaces decisions, success metrics, and constraints. It results in an auditable plan that clarifies objectives for stakeholders before implementation begins.
Yes, you can use a guided dialogue to capture constraints and success metrics for a bug fix. The structured Q&A flow is designed for any code change requiring clear objectives and acceptance criteria, ensuring the plan is well-defined before implementation.
You need a structured planning session whenever starting a feature or bug fix that carries ambiguity or risk. If the code change requires explicit objectives, constraints, and stakeholder alignment before writing code, a formal plan is necessary.
kireevkit15-sysRun a structured discovery interview and generate a design brief.
quan2005Compare code changes against story.md and design.md contracts before git commit.
luanCreate conventional Git commits and sync them with issue tracking systems.
AlphaCompositeClarify project intent and design goals through guided dialogue.
