使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/alexbruno/dev-skills --skill incremental-implementation開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Incremental Implementation
Deliver changes in thin, verifiable increments—one working slice at a time. Never write an entire multi-file feature in a single unverified pass.
Core Rule
One slice, one verification cycle. Do not start the next slice while the current slice has failing tests, type errors, or a broken build.
When to Apply
- Executing steps from
workflow/PLAN.mdor tasks fromworkflow/TASKS.md. - Any change touching two or more files or exceeding ~100 lines of code.
- Refactoring existing modules where behavior must remain intact at every step.
The Increment Loop
For each step in workflow/PLAN.md (or task in workflow/TASKS.md):
- Scope the Slice: Pick the smallest cohesive unit that delivers testable progress toward
workflow/SPEC.md. - Implement Minimally: Write only the code required for this slice—avoid speculative scaffolding for future slices.
- Test & Verify Immediately: Run targeted unit/integration tests, typecheck, and linter to confirm the slice works and introduces no regressions.
- Checkpoint: Update status in
workflow/PLAN.mdorworkflow/TASKS.md(e.g., markdone), and create a clean commit/checkpoint when appropriate so rollback is effortless. - Repeat: Advance to the next slice only after the current one is green.
Slicing Strategies
Choose the slicing strategy that best fits the work:
- Vertical Slices (Default): Implement one thin end-to-end capability across layers (e.g., schema -> service -> endpoint -> test) rather than building all backend files first and all frontend/test files last.
- Risk-First Slicing: Tackle the highest-uncertainty assumption, integration, or performance bottleneck in the earliest slice so surprises surface immediately.
- Contract-First Slicing: Define types, interfaces, and test assertions first, verify they compile/fail as expected, then implement the concrete behavior.
Guardrails
- No stacked brokenness: Fix failing checks in the current slice before moving on.
- Keep diffs reviewable: If a slice grows too large, split it into smaller sub-slices before continuing.
- Stay aligned with `SPEC.md`: Do not add unrequested features while implementing a slice.