使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
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.