Use when comprehensive verification checks need to run before completion. Runs all available checks (format, lint, type check, build, tests) in speed order and produces an evidence-based report. Example triggers — "run all checks", "verify the build", "pre-flight checks", "does everything pass".
The artifact schema contract for docs/plans/ / — the artifact inventory, the YAML frontmatter schema and phase enum, the repos.md and prd.md schemas, the topic-consistency invariant, ticketId scope, and the design-review record mechanics. Load when authoring or validating a pipeline artifact's frontmatter, checking…
Design-document authoring procedure for the design-author agent — the repo-scope confirmation flow, the autonomous open-questions resolution rule, and the design.md document template. Loaded when a design document is drafted or revised for the adversarial design review.
Generator-evaluator separation and review methodology — loaded by review agents to enforce fresh-context review discipline and gate verdicts; findings from the code, security, and docs reviewers are formatted per the conventional-comments skill. Trigger on "review this diff", "review these changes", "code review…
The Conventional Comments format for review findings — label and decoration syntax, code-directed comment style, and the issue/suggestion/nitpick comment types with literal examples. Load when writing, formatting, or labeling review comments, PR feedback, or reviewer findings.
Cross-vendor review pass at the code-review and design-review gates — machine-wide kill-switch, pinned full-access invocation of the codex and agy CLIs through a bundled script, verify-before-adopt disposition of external claims, and untrusted-output handling.
Artifact templates and decomposition procedure for the questioner agent — the task.md and questions.md body templates, the topic-slug rules, and the multi-repo detection flow. Loaded when a user's task description is decomposed into intent and neutral research questions.
Architecture Decision Record format — capturing the context, decision, alternatives considered, and consequences of a significant technical choice. Load when recording an architectural decision or writing an ADR.
Adversarially review a technical design document with fresh context. Dispatches the built-in read-only Explore subagent (clean context, no shared history with the design-author) against docs/plans/ /design.md and presents its verdict — APPROVE, REQUEST CHANGES, or COMMENT. The Review brief doubles as the pipeline's…
Engineering standards for design and implementation methodology -- loaded by planner, implementer, and code-reviewer agents for design-first workflow, implementation standards, and quality checklist.
File-location search strategy for the file-finder agent — glob by naming convention, content search, import tracing, directory exploration, and manifest checks, scoped to the vocabulary in questions.md. Loaded when files relevant to an area under investigation need to be found.
Git commit discipline — the Conventional Commits subject format, the 50/72 rule, and atomic single-purpose commits. Load when writing a commit message, committing an implementation slice, or preparing commits for a pull request.
Groom a project backlog in an issue tracker. Loads the whole board in bulk, computes a gap inventory instead of eyeballing one, verifies each candidate issue's factual claims against the code and the tracker, ranks the verified candidates by a stated four-tier heuristic, proposes an evidence-backed closure for an…
Slice-by-slice execution procedure for the implementer agent — dispatch modes (initial and review-fix), the slice-execution loop, TDD discipline, blocker handling, and the scope fence. Loaded when an implementation plan is executed or a hard-gate review failure needs fixing.
Guardrails for spawning nested sub-agents from inside a Team pipeline agent (Claude Code >= 2.1.172) — loaded by researcher, implementer, code-reviewer, and security-reviewer. Nested dispatch is a context-economy optimization, never a dependency.
Tactical planning methodology for the planner agent — the plan.md document template that expands each vertical slice into file-level steps, and the tactical rules that keep the plan scannable and scoped. Loaded when a structure is translated into the implementer's playbook.
Tear down local and remote branch state after a pull request is finished, in one of two modes. Mode A (merged): verify the PR actually merged, remove the branch's worktree, resync the default branch, and delete the local branch. Mode B (closed / abandoned): close the PR(s), then delete every trace — worktree, local…
Fetch every unresolved review thread on a pull request, verify each comment against the current code, react 👍 or 👎 to tell the reviewer whether it was useful, and rate confidence in one recommendation per item. An item rated above 90% confidence that passes every hard rule is applied, pushed, replied to, and…
Bring a feature branch up to date with its base without changing what the branch does: capture a pre-rebase check baseline, fetch, rebase onto the latest base, resolve each conflict from both sides' intent with the rationale recorded to disk, re-run the same checks, and treat any check that passed before and fails…
Verify a pull request's test plan with evidence-rated verdicts: extract every test-plan item, classify each by verification strategy, collect cited evidence per item (PASS / FAIL / PARTIAL at HIGH / MEDIUM / LOW confidence), and report a READY / NEEDS ATTENTION / NOT READY final verdict with follow-up recommendations.…
Watch your own pull request for review feedback: undraft it when the cue clearly says it is ready (an ambiguous cue watches the draft), take a baseline snapshot, then poll GitHub in 31-minute cycles for up to 24 hours and triage new feedback as it arrives — inline review threads and plain PR comments alike. Stops on…
Watch a pull request you are reviewing until your feedback is settled, re-review each settlement, then approve once: poll GitHub in 31-minute cycles for up to 24 hours until every review thread you opened is resolved and every plain PR comment you posted has a later push behind it, re-review each settlement against…
Optional PRD methodology — loaded by the questioner agent when a feature request is vague or complex enough to warrant a structured product spec alongside task.md. Produces a PRD artifact that downstream design-author work can ground decisions in.