IgnacioMarin402/spec-flow-plugin
Plugin Claude Code
A single-plugin marketplace for spec-flow. Install with claude plugin install spec-flow@spec-flow-marketplace.
IgnacioMarin402/spec-flow-plugin
Plugin Claude Code
A single-plugin marketplace for spec-flow. Install with claude plugin install spec-flow@spec-flow-marketplace.
IgnacioMarin402/spec-flow-plugin
Plugin Claude Code
Ships a feature only when a test that actually ran proves every requirement in its spec. Free-text requirement -> spec (you sign it off) -> plan -> review -> implement per milestone, gated by a lint/test/spec-trace loop that runs outside the model. For Node projects; your repo declares its test and lint commands in…
IgnacioMarin402/spec-flow-plugin
Skill Claude CodeCodex
Decide where a piece of reasoning belongs when writing or editing this engine — an invariant beside the code, a transition in the commit message, or a decision in decisions/. Use when adding a comment or a file header to hooks/, scripts/, commands/ or agents/, when a header has grown past what a reader needs, or when…
IgnacioMarin402/spec-flow-plugin
Instructions file
Instructions for IgnacioMarin402/spec-flow-plugin, covering working agreements for this repo, verify before you claim, and before you propose, proving a fix, changing one coupled contract is not a local edit and docs are checked, not trusted.
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…
IgnacioMarin402/spec-flow-plugin
Command
Show which model tier each spec-flow agent will run on in this repo, and which layer decided it. Optionally set or clear one agent's tier.
IgnacioMarin402/spec-flow-plugin
Command
Lightweight fix flow — triage a defect against specs/, then one implementer pass through the same external gate. No planner, no reviewer, no milestone map.
IgnacioMarin402/spec-flow-plugin
Command
Spec-driven multi-agent flow — free-text requirement -> spec (HITL) -> plan -> review -> implement per milestone, gated by an external lint/test loop.
IgnacioMarin402/spec-flow-plugin
Hook
Runs when a session starts, running node. From IgnacioMarin402/spec-flow-plugin.
IgnacioMarin402/spec-flow-plugin
Hook
Runs before the agent uses a tool for Bash, Bash, Write, Edit, Task, Agent, SendMessage, Task and Agent tool calls, running node (6 commands). From IgnacioMarin402/spec-flow-plugin.
IgnacioMarin402/spec-flow-plugin
Hook
Runs after a tool call finishes for Write, Edit, Task, Agent, Write, Edit, Read, Bash, Task and Agent tool calls, running node (3 commands). From IgnacioMarin402/spec-flow-plugin.
IgnacioMarin402/spec-flow-plugin
Hook
Runs when the agent finishes a response, running node. From IgnacioMarin402/spec-flow-plugin.
IgnacioMarin402/spec-flow-plugin
Skill Claude CodeCodex
Set up or repair this repo's spec-flow contract — run init, fill the fields it could not read, make the test command emit a report the engine can read, and prove the result with a green check. Use when a repo has no .spec-flow/config.json, when init left MISSING or REVIEW lines, when a run refuses to start because the…