Menu
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
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
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | grill-with-docs |
| description | A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go. |
A grilling session that also builds your project's domain model. Combines the
shared interview loop with the active domain-modeling discipline: sharpen
terminology, record architecture decisions, update CONTEXT.md inline.
Run the grilling skill to drive the interview.
As decisions crystallise, run the domain-modeling skill to keep the
domain model current (challenge terms, update CONTEXT.md lazily, offer
ADRs sparingly).
See .claude/skills/engineering/domain-modeling/CONTEXT-FORMAT.md for layout and detection. Create docs lazily only when recording needed.
Before broad reads, locate relevant files/symbols with Glob, Grep, or targeted file reads.
Prefer targeted Read with line ranges or block reads once the relevant area is known.
Read full files only when structure, ordering, or surrounding context is required for correctness.
Do not re-read unchanged files; use prior findings unless the file changed.
