incremental-implementation
Build in small, individually-verified increments that each leave the system working — instead of big-bang changes that fail mysteriously at the end. Use when implementing multi-part features, refactoring anything load-bearing, making large mechanical changes, or when past work produced huge diffs that were wrong somewhere unfindable. Produces the same end state as the big bang, reached through verified checkpoints you can stop at, ship from, or roll back to.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill incremental-implementation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Incremental Implementation Skill The big-bang failure is always the same story: three hours of changes, then "it doesn't work", then an hour of spelunking to find WHICH of forty edits broke it. Incremental work makes the *last five minutes* the only suspect, always. The discipline: every increment ends with the system working and verified — not "will work once the rest lands." ## What This Skill Produces - The target end state, reached via increments that were each verified green - **Stoppable points**: any checkpoint is shippable, pausable, or a rollback target - A change history where every step's intent is legible ## Increment Method 1. **Slice vertically to working states, not horizontally to layers.** "Data layer, then logic, then UI" means nothing works until everything does. Slice so each increment is a *thin working slice*: one endpoint end-to-end · one case handled fully · one call-site migrated. The test for a slice: after it lands, can you demonstrate something that works? 2. **Separate behaviour-preserving from behaviour-changing — always.** The cardinal rule: refactor OR change behaviour in one increment, never both. Prepare-with-refactor (verify: everything still pa
- What This Skill Produces
- Increment Method
- Output Format
- Increment plan: [target end state]
- Quality Checks
- Anti-Patterns
What does the incremental-implementation skill do?
Build in small, individually-verified increments that each leave the system working — instead of big-bang changes that fail mysteriously at the end. Use when implementing multi-part features, refactoring anything load-bearing, making large mechanical changes, or when past work produced huge diffs that were wrong somewhere unfindable. Produces the same end state as the big bang, reached through verified checkpoints you can stop at, ship from, or roll back to.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill incremental-implementation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.