Grill To Spec
Convert a completed grill-me session into a spec file. Captures only the task and the decisions locked during grilling — no implementation details, no invented decisions. Use when the user asks to write a spec from a grill, save grill decisions, or after a grill-me session concludes.
Install
$ agentstack add skill-retz8-pastiche-grill-to-spec ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-retz8-pastiche-grill-to-spec) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Grill to Spec
Convert a just-completed grill-me session into a spec file under _dev/docs/spec/.
File naming
Number first. Filename comes from the TODO number when available, otherwise name only. Do not ask the user about the path — derive it and proceed.
- Task (
**N.M**in TODO):_dev/docs/spec/task--.md - Phase:
_dev/docs/spec/phase--.md - No task number available:
_dev/docs/spec/.md
Hard rules
- Spec, not plan. Capture what was decided, not how to implement it. No task breakdown, no step-by-step, no file-by-file instructions.
- Only what was locked in the grill. If a decision did not come up explicitly in the grilling conversation, do not include it. Do not infer, do not extend, do not add "for completeness."
- No invented decisions. If the user did not state a preference on something, it is not in the spec. Surface it as an open item only if the user flagged it as open during grilling.
- No implementation details. No code, no command lines, no file syntax, no per-step procedure. The spec is a high-level overview of the locked task scope and decisions.
Required structure
#
## Scope
## Locked decisions
### 1.
### 2.
## Invariants
## Open items
Process
- Re-read the grilling conversation in context. Identify every decision the user explicitly accepted, rejected, or modified.
- Derive the target path per the File naming rules above. Do not ask, do not confirm.
- Write the spec directly to that path using the required structure. Do not display the draft to the user beforehand — just write it.
- Report the written path in one line. The user will redirect if revisions are needed.
What this skill never does
- Decompose the task into sub-tasks or a plan.
- Specify file contents, command flags, or code shapes.
- Add "recommended next steps."
- Re-open decisions the grill closed.
- Add decisions the grill did not cover.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: retz8
- Source: retz8/pastiche
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.