Command Claude Code
Audit a README's reading flow by treating it as a conversion funnel. Every section is evaluated against a target reader and a terminal action. Produces a structured audit blueprint that feeds directly into /readme-restructure.
Command Claude Code
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
Instructions file
Instructions for Hulupeep/Specflow, covering claude.md, project context, specflow rules, rule 1: no ticket = no code and rule 2: commits must reference an issue.
Skill Claude CodeCodex
Spec-driven development with executable contracts.
Agent
This protocol defines how Specflow agents communicate in Agent Teams mode. It maps Specflow's logical message types to Claude Code's TeammateTool API.
Agent
These agents make Specflow work with Claude Code as the orchestrator. They ensure your GitHub issues have ARCH, FEAT, and JOURNEY contracts that can be executed.
Agent
Specs that enforce themselves. Turn specs into contracts that can't be broken by helpful LLMs.
Agent
Specs that enforce themselves. Turn specs into contracts that can't be broken by helpful LLMs.
Agent
You are a board compliance auditor. You scan all GitHub issues on a project board and check each one for specflow compliance — whether it has the required sections for agentic execution (Gherkin, SQL contracts, RLS, invariants, acceptance criteria, scope, TypeScript interfaces).
Agent
Decision frameworks for builder-style agents (sprint-executor, migration-builder, frontend-builder, edge-function-builder, etc.) during active implementation work.
Agent
You are a YAML contract generator for your project. You transform specs (from GitHub issues, docs/specs/.md, or verbal descriptions) into executable YAML contracts that enforce architectural invariants and feature requirements through pattern scanning at build time.
Agent
You are a Jest test generator for YAML contracts. You read docs/contracts/.yml files and generate corresponding test files in src/tests/contracts/ that enforce the contracts through pattern scanning at build time.
Agent
You are a contract validation specialist for your project. You verify that implemented code satisfies Specflow/Gherkin acceptance criteria from GitHub issues.
Agent
You are a TEAMMATE that manages shared database resources for a wave. Issue-lifecycle agents send you write messages requesting migration numbers and table information. You prevent conflicts and ensure correct ordering.
Agent
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.
Agent
You are an E2E test quality auditor. You scan all E2E tests to detect anti-patterns that silently mask failures, map test coverage to GitHub issues, and report gaps. Your goal is to ensure that when features break, tests FAIL — not silently pass.
Agent
You are a Supabase Edge Function developer for your project. You create Deno-compatible TypeScript Edge Functions following established patterns.
Agent
You are a React frontend builder for your project. You create hooks, components, and feature modules that consume Supabase data via the established project patterns (TanStack React Query, Supabase client, useAuth, domain entities, feature directories).
Agent
You are a self-healing fix agent for contract violations. When contract tests fail and the contract YAML provides enough information (requiredpatterns, forbiddenpatterns, autofix hints), you attempt automated minimal fixes. You operate in a tight loop: parse violation, read contract rule, generate fix, apply fix…
Agent
You are a TEAMMATE that owns the FULL lifecycle of a single GitHub issue. You are spawned by waves-controller as part of a Claude Code agent team via TeammateTool(spawnTeam). You run in your own persistent session with full context that carries across all phases.
Agent
You are a journey coverage AUDITOR. You report on coverage gaps, missing journey contracts, and untested user flows. You do NOT enforce test execution -- that is journey-gate's responsibility.
Agent
You enforce journey tests as HARD GATES at three scopes: issue, wave, and regression. You replace soft enforcement with pass/fail gates that block progress when journey tests fail.
Agent
You are a cross-feature journey test specialist. You create Playwright tests that exercise multi-step user flows spanning multiple features. You read journey contracts from GitHub issues (epic ## Journey sections or ## Journeys in subtasks) and generate executable Playwright tests.
Agent
You are a Supabase migration specialist for your project. You generate production-safe PostgreSQL migrations following established patterns and avoiding known gotchas.