The brooks-lint verification gate. Runs npm run validate, npm test, and npm run evals, then cross-checks the documents the validator can't fully diff — the four plugin manifests, all six README badges, the docs landing-page JSON-LD, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports…
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
Authors and edits brooks-lint skill content — the six shipped skills (skills/{name}/SKILL.md + {name}-guide.md) and the shared framework under skills/shared/. Knows the repo's hard conventions: the Iron Law finding form, the SKILL.md Setup→Process→Mode-line shape, guide step continuity, and the mandatory "Do NOT…
Implements backend features - entities, services, controllers, validators, tests, migrations. Use for .NET implementation work that stays within src/backend/.
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
Implements features that span both backend and frontend - new API endpoints with their frontend consumers, cross-stack refactors, type regeneration. Use when work touches both src/backend/ and src/frontend/.
Implement a ReviewFlow feature via TDD inside-out. Receives a validated plan (docs/plans/ .plan.md) and spec (docs/specs/ .md), implements all layers with RED-GREEN-REFACTOR, self-reviews, and persists a report. Triggers when the user says "implement feature", "start implementation", "implement spec", or "run…
Plan a ReviewFlow feature implementation. Analyzes a spec in docs/specs/, maps it to Clean Architecture layers (Entity → Use Case → Gateway → Controller), and produces a structured plan in docs/plans/ .plan.md. Triggers when the user says "plan feature", "plan implementation", "analyse spec", or "create plan for".
Use proactively after larger refactors, new modules, or changes that introduce cross-package imports, exports, parts, or dependencies. Audits the diff for package-graph and clean-architecture boundary violations before they ship.
Use this agent to design or critique agentic primitive modules (skills, persona scoping files, scope-attached rule files, orchestrator workflows). Activate BEFORE drafting any natural-language primitive content, when refactoring existing modules, or when assessing whether a primitive change adheres to PROSE, Agent…
Use to reconcile the SKRAFT handbook (docs/site/) with the shipped plugin sources — detect documentation drift (missing/empty/stale pages, FR/EN parity breaks, broken multi-level menu, ordering gaps, orphan agents/skills/lenses, invalid citations) and repair it through a pull request. Dispatched by the gh-aw docs…