incremental-implementation

Deliver multi-file project changes in small verifiable slices.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/zxyycom/docnav --skill incremental-implementation-zxyycom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incremental-implementation
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/incremental-implementation
Command: npx skills add https://github.com/zxyycom/docnav --skill incremental-implementation-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

通过小步增量交付变更,降低在多文件改动、垂直切片工作流、重构、任务拆分、代理交接等场景中的风险,同时确保每一步都可验证。

Core Features & Use Cases

  • Small vertical slices: 以最小可用功能切片推进,每次只实现一个明确目标并可独立验证。
  • Per-slice verification: 每个 slice 完成后执行验证命令、测试或手动回放,确保契约不被破坏。
  • Clear scope discipline: 使用 Owned files、Read-only context、Out of scope、Shared contracts 清晰界定边界,避免范围蔓延。
  • Handoff & collaboration: 支持多人协作、任务分解与边界记录,便于 agent handoffs 与工作交接。

Quick Start

逐步实现一个最小可验证的增量 slice,完成后立即测试并在通过验证后再扩展下一片。

Frequently Asked Questions about incremental-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage risk when making multi-file changes in a project?

Incremental delivery manages risk by implementing small vertical slices, ensuring each step remains independently verifiable and rollback-ready before expanding scope.

What is incremental delivery for vertical slices?

Incremental delivery for vertical slices progresses changes through minimal functional units, applying defined verification commands after each step to ensure contracts remain unbroken.

How do I break down refactoring tasks for safe agent handoffs?

Breaking down refactoring for agent handoffs requires defining clear slice ownership, minimal scope, and a documented progression plan to ensure seamless task boundary records and collaboration.

Does incremental implementation work for complex refactoring?

Incremental implementation suits complex refactoring by enforcing clear scope discipline using owned files, read-only context, and shared contracts to prevent scope creep across multiple steps.

When should I not use small step increments for project delivery?

Avoid using small step increments for project delivery when work can be completed safely in a single step, as the overhead of slice ownership and per-slice verification becomes unnecessary.