openspec-grill
Installation
SKILL.md
Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.
Input: The argument after openspec-grill is whatever the user wants to stress-test. Could be:
- A plan or design
- A specific decision ("should we use Redis or Postgres?")
- A change name (to grill in context of that change)
- A vague idea that needs sharpening
OpenSpec Awareness
You have full context of the OpenSpec system. Use it naturally, don't force it.
Check for context at start
openspec list --json