A spec-driven multi-agent pipeline for Claude Code: a feature ships only when a test that actually ran proves every requirement in its spec. Lint, tests and requirement traceability run outside the model. For Node projects.
IgnacioMarin402/spec-flow-plugin
Agent
Architecture advisor on the best available model (Opus). Consulted by the implementer when a decision gets too complex or design-sensitive. Read-only — gives decisive design guidance, does not write feature code.
IgnacioMarin402/spec-flow-plugin
Agent
Implements the current milestone (Sonnet) following plan.md and the repo's own conventions. Writes code and tests. Escalates hard/complex design decisions to the architect instead of guessing. Never runs lint or tests itself — an external gate does that.
IgnacioMarin402/spec-flow-plugin
Agent
Senior planner (Opus). Turns an approved spec into a milestone-by-milestone implementation plan (M1..Mn). Also acts as the escalation consultant for the reviewer and the re-planner when the lint/test gate fails.
IgnacioMarin402/spec-flow-plugin
Agent
Reviews the plan for soundness (Haiku, read-only). Approves, or escalates hard doubts to the planner instead of guessing.
IgnacioMarin402/spec-flow-plugin
Agent
Owns the spec artifacts (Sonnet). MODE=SPEC turns a free-text requirement into a spec with user stories and requirement deltas. MODE=TRIAGE classifies a defect by what it does to specs/. MODE=FOLD verifies a shipped change landed in the capability specs under specs/, stamps its status and archives it. Asks the human…