prompts/squad/skills/quality-gate/SKILL.md
Enforce the -warnaserror build + 95% coverage test gate on every squad [DONE]. Use this before any specialist (Coder, Tester, Reviewer, Infra) marks a phase complete.
npx skillsauth add imabusyman/CodebrewRouter quality-gateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Every squad phase that produces code must pass this gate before [DONE].
dotnet build --no-incremental -warnaserror
dotnet test --no-build --collect:"XPlat Code Coverage"
Both must succeed. If either fails, emit [BLOCKED] with the failure summary and the failing path.
#nullable disable. If the compiler emits a nullable warning, fix the underlying null-handling.#pragma warning disable. Silenced warnings are a CRITICAL review finding.CS8600–CS8629 (nullable reference-type warnings).95% line coverage on the production files listed in the envelope's "Files you may edit" block. Compute from:
TestResults/<guid>/coverage.cobertura.xml
Grep for <class name="<fully-qualified>" blocks and compute line-rate per file. Line rate < 0.95 on any envelope-listed file → [BLOCKED] with the file + percentage.
[DONE].[BLOCKED] regardless of what Tester said.dotnet build --no-incremental -warnaserror is green before [CHECKPOINT] or [DONE].Use FullyQualifiedName~ filters for inner-loop iteration:
dotnet test --no-build --filter "FullyQualifiedName~<YourNewTestClass>"
Once targeted passes, run the full suite + coverage for the gate.
development
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
development
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
development
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
testing
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.