incremental-approach
Build in verified increments rather than one speculative block: smallest viable change first, verify, then extend; prototype the risky part before committing to a design; batch edits to one file into
SKILL.mdinternal/builtins/universal/token-efficiency/skills/incremental-approach/SKILL.md
GitHub- Start with the smallest viable change, verify it works, then extend. Implement one piece, test, move on.
- Avoid generating large blocks of speculative code.
- When uncertain about an approach, prototype the critical part before committing to the full implementation.
- Batch multiple edits to the same file into one operation, and prefer multi-file search over reading files one by one when exploring.