dev-cycle

Executes a plan, TDD implement, review, and simplify pipeline for multi-file code changes.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill dev-cycle-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-cycle
Source: https://github.com/visdomtech/skills/tree/main/dev-cycle
Command: npx skills add https://github.com/visdomtech/skills --skill dev-cycle-visdomtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial code changes often ship with unclear plans, untested fixes, and undetected regressions. This Skill enforces a disciplined sequential pipeline—setup, planning, test-driven implementation, multi-axis review, and simplification—so every change is validated at explicit exit gates before commit. ## Core Features & Use Cases - Parallel Multi-Agent Planning: Synthesizes implementation plans via three parallel planning agents, or adopts a supplied plan file, with mandatory root-cause analysis for bug fixes. - TDD Implementation with Per-Phase Commits: Runs RED-GREEN-REFACTOR cycles on a faster model, committing scoped changes at each phase exit gate. - Deep Multi-Axis Review: Dispatches fresh-context review subagents across correctness, security, architecture, and lifecycle axes, including shared-state consumer tracing. - Use Case: When fixing a regression whose root cause is unknown, the pipeline forces an evidence-backed root-cause analysis, a reproduction test, and a full review before any commit lands. ## Quick Start Use the dev-cycle skill to implement this change through the full plan, implement, review, and simplify pipeline.

Frequently Asked Questions about dev-cycle

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

FAQPage Schema
How do I run a structured plan-implement-review pipeline for a code change?▼

Invoke the dev-cycle skill with your change description. It verifies your git branch state, classifies complexity, generates or adopts a plan, implements via TDD, runs a multi-axis review, simplifies, and commits each phase separately.

How to fix a bug when the root cause is unknown?▼

The pipeline's Diagnose-and-Fix mode requires a full root-cause analysis first: symptom, reproduction steps, evidence-backed root cause with file:line citations, and discarded hypotheses. Implementation cannot proceed on a speculative fix.

Can I use an existing plan file instead of generating a new one?▼

Yes. Supplying a plan path triggers Adopt mode, which loads and validates the plan against the output contract—ordered tasks under 5 files each, acceptance criteria, risks, and rejected alternatives—before requesting approval.

Does the pipeline work in a single-model environment?▼

Yes. When distinct high-reasoning and faster models are unavailable, the current model is assigned to all phases and the pipeline proceeds without a model confirmation prompt.

When should I not use this pipeline?▼

Skip it for trivial changes of three files or fewer with unambiguous requirements—those use a fast path that skips planning. Also avoid it when a change cannot be verified with build, lint, typecheck, and tests.