Developer Workflows

Developer Workflows

The phase-gated developer loop — /setup · /plan · /work · /review · /release · /bugfix — extracted from agentm as a standalone native plugin. The base the other plugins enhance.

Full primitive and hook detail: development-lifecycle design.

How it composes

• Standalone — installs and works on its own; requires: [].
• The base others enhance — developer-safety's control hooks and code-review's reviewer engage across the phase loop when installed alongside it.
• Hosts — phase commands, agents, output-style, and rule are host-symmetric; harness-context-session-start and compact-nudge-resume hooks are Claude-only (Antigravity limitations).

Why it works

Discrete plan → work → review → release gates beat freestyling the whole lifecycle in one pass: context is ephemeral so state lives on disk; /work runs the task list autonomously, single-threaded and gated by a per-task safety check; /review is adversarial by design — a reviewer primed to assume bugs finds real ones. See Why phase-gating and Why adversarial review.

Related

• Evaluator — the /review rubric grader's dispatch contract.
• Named plans · See every active plan — the multi-plan surface.
• Spawn a worker in a worktree · Run isolated tasks · Integrate a worker — the worktree lifecycle.
• Developer Safety · Plugin anatomy — the sibling safety plugin + the shared plugin structure.
• Why phase-gating — why the loop is gated.
• Development lifecycle design — the full design, including hooks and find_process_seam.py.
• Developer Plugin Suite design — the developer-workflows / safety / code-review split.

Architecture · Plugins · Home