spec-flow

Plugin spec-flow from marketplace rustyrazorblade-plugins in rustyrazorblade/skills. Commands read from the repo's manifest — today.

Skills (10)

• activate

  Activate a groomed GitHub issue for development — claim it, review it with the owner (scope/acceptance-criteria freshness + backlog overlap, issue-specific questions, skippable via owner-instructions), run architect + domain-expert design concurrently then stress-test the result with design-critic,

• address

  Address the owner's GitHub review comments on an issue's PR — pull the comments, fix them in the issue's worktree, push, and reply per review thread. Fourth stage of the flow delivery workflow (see docs/workflow.md). Owner-invoked when they return after reviewing; never polls.

• adopt-tiering

  One-time migration that splits a repo's existing test suite into a fast unit tier and a slow integration tier — for a repo whose own spec-flow/TESTING.md policy chooses that split, not an assumption the pipeline makes. Classify tests by evidence (container/I-O/timing) and let the compiler + test tim

• archive

  Check the buildup of un-archived OpenSpec changes waiting on the default branch (one per merged-and-finalized issue) against a threshold (default 5, overridable), and — once confirmed with the owner — spawn a dedicated background worker to sync and archive them all in one pass and land one PR. Owner

• board

  Report status across all in-flight delivery pipelines — every issue by lifecycle label with its priority, stage, live issue-manager session, and PR state — and highlight what's next, what's blocked on the owner, and what's stalled. Use when the owner asks 'where do things stand' or 'what should I wo

• finalize

  Finalize a merged issue — close the GitHub issue, remove its lifecycle/coordination labels, close and clean any issue recorded to close with it, and remove the issue's git worktree. Final stage of the flow delivery workflow (see docs/workflow.md). Runs once the FEATURE PR has merged — by the owner's

• groom

  Turn a rough idea into a scoped, labeled GitHub issue ready for the delivery pipeline. Use when the owner wants to capture a todo, feature, or bug as a real backlog item with scope, acceptance criteria, and a priority. Refines the idea over as many rounds as it takes — each round a fresh `product-ma

• implement

  Implement an approved issue — run tdd-developer → review panel → fix loop → build-engineer → docs polish in the issue's own worktree, then push the branch and open a PR. Defaults to an agent team led by issue-manager (SPEC_FLOW_IMPLEMENT_MODE=team, requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1); f

• setup

  Interactively bring a repo onto spec-flow's Prerequisites — OpenSpec init, gh auth, the label vocabulary, the agent-teams env var, the seam-visualization preference, the refactor circuit breaker, the .gitignore entries, the repo's own spec-flow/TESTING.md test and CI policy (proposed, confirmed with

• sync-ci

  Pull the branch's latest CI test failures into the issue's local flagged set — download the spec-flow-failures artifact from the most recent CI run and append the failing test ids to .spec-flow/flagged-tests in the worktree, so the local loop runs them for the rest of the branch. Exits cleanly, doin

Subagents (13)

• architect

  Design specialist for the flow delivery pipeline. Takes a refined unit of work (scope + acceptance criteria) and produces a design proposal — structure, module boundaries, data model, key interfaces, and the trade-offs behind them — that feeds the OpenSpec proposal. Owns the HOW; reviews for SOLID a

• archive-batch

  One-shot bulk archiver for spec-flow's OpenSpec changes — syncs and archives every OpenSpec change waiting on the default branch in a single pass, then opens and merges one PR. Launched by the central project-manager (via scripts/spawn-archive-batch.sh), as its own separate background Claude Code pr

• build-engineer

  Build and tooling specialist. Use for build configuration, dependency management, multi-project builds, custom tasks, build performance, CI build steps, and diagnosing build failures. Adapts to the project's build tool (Gradle/Maven/Bazel, Cargo, npm/pnpm, Go, etc.). Spawn it with a concrete build p

• code-reviewer

  Project-agnostic correctness reviewer for the flow delivery pipeline. Invokes the built-in /code-review skill to hunt correctness defects ONLY — logic errors, off-by-one/boundary/edge-case mistakes, unhandled error paths, panics/unwrap on fallible values, incorrect concurrency or async ordering, res

• design-critic

  Adversarial reviewer of a DESIGN, before any code exists. Takes the architect's design proposal plus the issue's scope and acceptance criteria, and actively tries to break the plan — unstated assumptions, missing edge cases, failure and concurrency modes the design doesn't address, acceptance criter

• issue-manager

  Per-issue delivery lead for the flow pipeline — owns ONE issue end-to-end (activate, both owner stops, implement, address, finalize) once the central project-manager launches it, via scripts/spawn-issue-manager.sh, as its own separate background Claude Code process. The owner attaches to it directly

• observability-reviewer

  Project-agnostic observability reviewer for the flow delivery pipeline. Audits whether a change's new code paths and failure modes are diagnosable in production — structured logging at the right levels (no secret/PII leakage), metrics on operations and error paths, tracing/span coverage around new I

• product-manager

  Idea-refinement specialist for the flow delivery pipeline. Turns a rough idea, bug report, or feature request into a tight, well-scoped unit of work — a clear problem statement, explicit in/out scope, and testable acceptance criteria written as observable WHEN/THEN outcomes that later become the spe

• project-manager

  Central coordinator for the flow delivery pipeline — the agent the owner talks to for cross-issue state (the board), grooming new work, and deciding what's next. Does NOT drive an individual issue's activate/implement/address/finalize inline; when the owner wants to start or resume work on a specifi

• reviewer

  Project-agnostic code reviewer for the flow delivery pipeline. Reviews a branch diff against its committed OpenSpec spec AND the repo's own documented conventions (its CLAUDE.md / CONTRIBUTING / style guide). Spawn it with a worktree path, a base ref, and the change name; it returns structured findi

• security-reviewer

  Project-agnostic security reviewer for the flow delivery pipeline. Invokes the built-in /security-review skill. Self-gates — first enumerates whether the diff touches any security-relevant surface (input parsing, multi-tenant isolation, authn/authz, external endpoints, secrets/sensitive-data exposur

• tdd-developer

  Software development agent that works test-first (TDD) and designs to SOLID principles. Use for implementing features, fixing bugs, or refactoring where you want disciplined red-green-refactor cycles and clean, well-factored object-oriented design. Spawn it with a concrete unit of work (a feature, a

• test-rigor-reviewer

  Project-agnostic test-rigor reviewer for the flow delivery pipeline. Judges regression-catching value per unit of test cost in BOTH directions — flags MISSING coverage (a change's public surface and observable side effects lacking antagonistic, regression-exposing tests, not just happy-path calls) A

Similar plugins