Menu
Use when creating a new document of a configured type at the most manual authorship level -- AI creates the file and frontmatter, surfaces intent and section guidance, then hands the body back to the human.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | scaffold |
| description | Use when creating a new document of a configured type at the most manual authorship level -- AI creates the file and frontmatter, surfaces intent and section guidance, then hands the body back to the human. |
CREATE THE SHELL, HAND THE BODY BACK
--json. Read parent/relation/gate facts from the CLI, never from .lazyspec/ graph files directly. On failure, check --help before retrying.
The authorship order is scaffold < co-write < generate. A type's authorship value in config (human, assisted, generated) is the ceiling -- the highest verb permitted for that type.
Scaffold is the floor of that order, so it is permitted on every authorship value. Scaffold never refuses on ceiling grounds. Even a type whose ceiling is human can be scaffolded; that is exactly the manual case scaffold exists for.
lazyspec config --json -- read the target <type> entry: its intent (what the doc is for), its authorship ceiling (for confirmation only -- scaffold proceeds regardless), its parent_type, and the section guidance available from its template.lazyspec status --json -- see what already exists and locate the parent document to link to.lazyspec context --json -- understand the chain around the user's current position so the new document lands in the right place.lazyspec create <type> "<title>" --author <name>, where <type> is the parameter read from config (e.g. in the shipped default config a type named rfc, but never assume that name -- read it).parent_type and a parent exists, lazyspec link <new-id> implements <parent-id> -- using the configured relation name from relationships (the default config uses implements; read it, don't bake it).intent from config and the per-section <!-- guidance --> comments from the scaffolded body. Tell the human these are the sections to fill in.