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…
Reviewer lens: verifies every citation on a handbook page resolves to citations.yml (author, work, year), the referencetemplate required blocks are present on reference pages, and craft vocabulary matches the source skill verbatim. Backed by the deterministic check-citations.mjs tool.
You are an internal worker dispatched by skraft-docs-orchestrator. You make ONE type: derived page (and its FR/EN mirror) faithfully reflect its plugin source.
Reviewer lens: reads handbook pages with one question — is each page written in exactly the Diátaxis mode of the menu section it lives in (tutorial | how-to | explanation | reference), with no mode mixing?
You are an internal worker dispatched by skraft-docs-orchestrator. You write ONE complete type: editorial page (and its FR/EN mirror) as finished, readable prose.
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…
Reviewer lens: reads a handbook page pair with one question — do the FR and EN versions mirror each other (same English basename, same heading structure, equivalent content, neither side ahead)?
You are an internal worker dispatched by skraft-docs-orchestrator. You answer ONE question per item: where does this belong in the book, and in what order? Your only output is a patch to docs/site/data/book.yml.
Reviewer lens: verifies the handbook's multi-level menu is well-formed — Diátaxis mode per part, ordered sections and pages, individual reference items present, and no internal link pointing to a page that does not exist. Backed by the deterministic lint-nav.mjs tool.
The DISTILL reviewer verifies that scenarios cover acceptance criteria without modifying the .feature files. CQS applies: reading a scenario to evaluate it must not transform it.
BDD scenarios are executable specifications. They capture expected behaviour in a language shared between developers and domain experts, eliminating the ambiguity of textual specifications.
The reviewer is a read-only agent. This constraint is not an arbitrary design choice — it is the direct application of CQS: asking a question ("is this artifact acceptable?") must not change the answer.
The discoverer applies explicit review criteria for every triage decision. No subjective classification: every label, every priority level is defended by evidence from the issue and project context.
The planner treats scope, time, and quality as conscious variables. Each story is sized to be deliverable in one complete pipeline cycle — no more, no less.
Makes a brownfield service SAFE TO CHANGE before refactoring: API contracts, Microcks mocks, golden-master characterization tests. Standalone workflow.
Drives a disciplined refactor (Mikado or Strangler Fig) of a brownfield component that already has a safety net, keeping it green at every commit. Standalone workflow.
The orchestrator is a pure coordinator. It owns no business logic, no artifact-writing capability. This separation applies CQS at the system level: commands go to executors, queries come back from reviewers.
This page is not an agent to invoke — it documents the DELIVER loop combining the software-engineer and the software-engineer-reviewer.
8 4d agoA0 tokens
GPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: