agentleFS
JBSommelingJBSommeling/claude-config/.agents/skills/incremental-implementation/SKILL.md

incremental-implementation

Skill0 starsChanged 29 days agoMITView on GitHub

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when a task feels too big to land in one step.

79 other projects use a version of this, 54 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use constraint-driven-development, deprecation-and-migration and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MrCipherSmithSkill

    constraint-driven-development

    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.

    Also in 14 projects that use this

  • HK-hubSkill

    deprecation-and-migration

    Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

    Also in 36 projects that use this

  • HK-hubSkill

    observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

    Also in 29 projects that use this

  • seikaikyoSkill

    doubt-driven-development

    對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。

    Also in 33 projects that use this

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 30 projects that use this

  • thunderkdsSkill

    review-diff

    Generate a Markdown review file with C4 architecture diagrams and code walkthrough for the current git changes

    Also in 3 projects that use this

  • +1 more from HK-hub

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 74 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing any code: "What is the simplest thing that could work?" Three similar lines is better than a premature abstraction.

    line 34
  2. Distinctive:

    After each increment, the project must build and existing tests must pass.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 74 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Incremental Implementation

Build in thin vertical slices — implement one piece, test it, verify it, commit, then expand. Each increment leaves the system in a working, testable state.

The Increment Cycle

Implement → Test → Verify → Commit (orchestrator, inline) → Next slice

For each slice:

  1. Implement the smallest complete piece of functionality
  2. Test — run the test suite (or write a test if none exists)
  3. Verify — tests pass, build succeeds
  4. Commit — descriptive message
  5. Next slice — carry forward, don't restart

Slicing Strategies

Vertical slices (preferred): One complete path through the stack per slice. Each delivers working end-to-end functionality.

Risk-first: Tackle the riskiest or most uncertain piece first. If it fails, you discover it before investing in the rest.

Contract-first: Define API contract first, then backend and frontend can develop in parallel against it.

Rules

Simplicity First

Before writing any code: "What is the simplest thing that could work?" Three similar lines is better than a premature abstraction. Implement the naive, obviously-correct version first.

Scope Discipline

Touch only what the task requires. Don't clean up adjacent code, refactor imports in files you're not modifying, or add features not in the spec. If you notice something worth improving, note it — don't fix it.

One Thing at a Time

Each increment changes one logical thing. Don't mix a new component, a refactor, and a config change in one commit.

Keep It Compilable

After each increment, the project must build and existing tests must pass.

Increment Checklist

After each increment:

  • The change does one thing and does it completely
  • All existing tests still pass
  • The build succeeds
  • The new functionality works as expected
  • The orchestrator has committed the change directly inline (git add / git commit) with a descriptive message — no subagent spawned solely to commit

Red Flags

  • More than 100 lines written without running tests
  • Multiple unrelated changes in a single increment
  • Skipping test/verify step to move faster
  • Build or tests broken between increments
  • Building abstractions before the third use case demands it
  • Touching files outside task scope "while I'm here"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.