Menu
Use when critiquing a document against its intent and acceptance criteria, or reviewing completed work, before advancing status.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when carrying out the work a delivery document describes -- the build loop -- against its task breakdown and acceptance criteria.
Use as the entry point for any work, including reported bugs, defects, and unexpected behaviour. Reads the configured DAG and the user's position, then dispatches the right verb -- advancing within the current document automatically but stopping at type boundaries.
Use when moving a document to its next status along the type's lifecycle DAG, maintaining links and checking gates at the transition.
Use when drafting a document of a configured type collaboratively -- AI proposes a draft body, the human edits, iterate -- up to the type's authorship ceiling.
Use when adding a new custom document type to a lazyspec project. Interviews the user to co-author the type's methodology -- intent, authorship, lifecycle, gates, relations -- then writes its enriched template and `[[types]]` config via the config-write CLI. One type per run.
Use when running a criteria-based review (health check, security audit, accessibility review, pen test, bug bash, spec compliance). Creates an Audit document with findings and presents them to the user for triage.
| name | review |
| description | Use when critiquing a document against its intent and acceptance criteria, or reviewing completed work, before advancing status. |
CONFORMANCE FIRST, QUALITY SECOND
--json. Read type/lifecycle facts from the CLI, never from .lazyspec/ graph files directly. On failure, check --help before retrying.
lazyspec config --json -- read the type's intent (the bar to critique against) and its lifecycle (to know which status review precedes, so the pass-route to /advance targets the right edge).lazyspec show <id> --json -- read the document and its acceptance criteria.lazyspec context --json -- read the chain (parent intent and ACs) so conformance is judged against the right spec.Two-stage critique:
Stage 1 -- Conformance. Does the document satisfy its declared intent and its acceptance criteria? For work being reviewed, verify each acceptance criterion with fresh evidence run in this session. Block on any conformance failure.
Stage 2 -- Quality. Only after conformance passes: critique quality -- clarity, correctness, cohesion, and (for work) test quality. Flag unjustified tradeoffs.
Express targets generically: "the document's acceptance criteria", "its declared intent". No type name is baked in.