Run implementation work from a tracked issue with explicit scope, branch intent, validation steps, and closeout evidence.
Run the noslop pre-commit quality gate, interpret failures, and enforce content-aware protection rules before every commit.
Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when…
Run the noslop pre-PR quality gate and handle the noslop-approved escape hatch for intentional config weakening before opening a pull request.
Review third-party skill repos for format fit, provenance, and first-party adoption paths without treating them as direct harness dependencies.
Install and configure noslop quality gates in an existing repository, including git hooks, CI workflows, and Claude Code guardrails.
Inspect failing GitHub Actions checks, isolate the actionable failure, and turn it into a concrete fix path with verification steps.
Interpret the output of `specgraph verify` and explain what each status means and what to do next.
Align design artifacts with code tokens and component APIs so spacing, color, type, and states stay consistent through implementation.
Write correct @spec JSDoc annotations in source files to link code to specgraph spec documents and produce E0 evidence.
Plan an MCP server with clear tool scope, auth model, error behavior, evaluation approach, and rollout boundaries.
Write a specgraph evidence waiver for a spec requirement that cannot currently be satisfied, with a clear justification and expiry plan.
Address GitHub PR review threads or issue comments with explicit comment selection, repo-grounded fixes, and concise reply-ready summaries.
Translate a Figma screen or component into an implementation plan covering structure, states, constraints, and component boundaries.
Check whether a change is ready for review by testing the claimed behavior, summarizing risk, and naming any gaps reviewers should know about.
Analyse specgraph verify output and identify what evidence is missing to advance specs to their next state.
Structure a clean handoff between workflow agents with explicit outputs, open questions, and next-owner guidance.
Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.