fast-iterate

Implements rapid vertical-slice coding with smoke-first TDD and minimal-diff verification loops.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fusuyfusuy/dot-agents --skill fast-iterate-fusuyfusuy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fast-iterate
Source: https://github.com/fusuyfusuy/dot-agents/tree/main/skills/fast-iterate
Command: npx skills add https://github.com/fusuyfusuy/dot-agents --skill fast-iterate-fusuyfusuy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It eliminates planning bloat, mock-heavy testing, and speculative over-engineering when shipping features, fixing bugs, or refactoring code, replacing them with tight, machine-verifiable feedback loops. ## Core Features & Use Cases - 4-Step Rapid Loop: Trace and orient on a targeted code slice, write one failing smoke check, climb the Ponytail minimal-diff ladder (YAGNI to minimal diff), then verify with exit 0. - Smoke-First TDD: Enforces a single runnable assertion proving the bug or exercising the boundary contract instead of elaborate mock factories and fixture scaffolds. - Anti-Pattern Guardrails: Blocks speculative generality, defensive null-checking, test theater, and prose bloat while capping cyclomatic complexity at 10 and nesting depth at 3. - Use Case: When fixing a bug in a large codebase, trace the execution flow, write the smallest assertion that reproduces the failure, apply the smallest working diff at the root cause, and confirm the check passes with exit 0. ## Quick Start Ask the agent to fix a specific bug or implement a small feature using the fast-iterate protocol with a failing smoke check and minimal diff.

Frequently Asked Questions about fast-iterate

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

FAQPage Schema
How do I implement a feature quickly without over-engineering?▼

Follow the Ponytail ladder: check YAGNI first, then reuse existing helpers, standard library, native platform features, and installed dependencies before writing new code. Stop at the first rung that solves the problem and ship the smallest working diff.

How to practice TDD without writing heavy mocks?▼

Use smoke-first testing: write one runnable assertion that reproduces the bug or exercises the boundary contract directly. Avoid mock factories and fixture scaffolds for code that does not exist yet, and verify the check fails before implementing.

When should I use fast-iterate instead of a full code review process?▼

Use fast-iterate for everyday coding, bug fixes, targeted features, and surgical refactoring. Reserve multi-phase review protocols like boundary-review for system-wide architectural audits, security reviews, and pre-release sign-offs.

What are the limitations of minimal-diff development?▼

Minimal-diff execution is not suited for system-wide architectural changes or cross-subsystem work requiring coordinated planning. Deliberate shortcuts must be marked with a ponytail annotation stating the ceiling and upgrade trigger.

Why should bug fixes target the root cause instead of callers?▼

Patching individual callers defensively duplicates logic and leaves the underlying defect intact. Grep all callers of the touched function, fix once at the source, and the entire call graph benefits from a single surgical change.