agentsclimarketplace

Grill to spec

Skill patinaproject/skills/skills/grill-to-spec

Grill a design to settled, then hand it to `/to-spec` with its ADR and glossary changes as file-ready proposals. Use when grilling anywhere but the branch that will implement the outcome.From its SKILL.md

Install
npx -y skills add patinaproject/skills --skill grill-to-spec

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, as published. Nobody here has run it

Grill To Spec

Grill a design to settled, then hand the whole outcome to /to-spec for publication: the spec, and every documentation change the design resolved, as a proposal — complete file-ready text the implementing branch can apply verbatim.

The worktree stays scratch: this skill leaves it as it found it, and the decision travels out through the spec instead.

Required Child Skills

  • grilling: the interview loop that walks the design tree to settled.
  • domain-modeling: supplies the capture rules and the CONTEXT-FORMAT.md and ADR-FORMAT.md each proposal is written to. Take its formats and its bar for recording an ADR; leave its inline "update CONTEXT.md right there" step, which this skill replaces with a proposal on the issue.
  • to-spec: the operator runs it to publish. It is user-invoked, so confirm it is installed and name it in the hand-off rather than calling it.

If one is missing, stop and report its name with install guidance:

npm_config_ignore_scripts=true pnpm dlx skills@latest add mattpocock/skills --skill grilling domain-modeling to-spec -y

Workflow

  1. Grill to settled. Record git status --porcelain as the worktree baseline, then run grilling, keeping every documentation change it resolves in the session as material for step 2. Done when grilling reaches its own settled bar.

  2. Draft a proposal per resolved doc change. A glossary term the session pinned down, and a decision that clears domain-modeling's bar for recording an ADR, each become one proposal, the unit the hand-off indexes. Write the text to the format domain-modeling names — CONTEXT-FORMAT.md for a glossary entry, ADR-FORMAT.md for a decision — and follow the target repository's own ADR naming scheme when it documents one. That text is the proposal's draft: one fenced block in the conversation, labelled with its destination path and carrying the complete text that belongs there.

    In a repository with a CONTEXT-MAP.md, a term belongs to its context's CONTEXT.md, and a decision to that context's docs/adr/ when it binds only that context or the root docs/adr/ when it binds the system.

    When grilling resumes after drafting and reopens a settled term or decision, re-draft its one proposal. A proposal's newest draft is the live one, and the drafts it superseded stay in the conversation as history.

    Done when every term and decision the session settled is accounted for: drafted as a proposal, or named as a deliberate skip with its reason. A design that settled neither yields no proposals; carry on to the spec.

  3. Confirm the worktree. git status --porcelain matches the step 1 baseline, proving the grilling left nothing behind to commit.

  4. Hand off to the operator. This is where the run ends: publishing is theirs. Index the proposals under one Proposed doc changes heading: one line each, naming the term or decision, its destination path, and a one-sentence summary, plus the count. The full text stays where step 2 drafted it: /to-spec synthesizes from this conversation, so it reads each proposal's live draft there, and the tracker issue it publishes is the canonical copy from then on. Print a draft in full only when the operator asks to see one.

    Close by telling them to run /to-spec to publish the spec with those drafts inside it, carried over unchanged — the implementing branch applies them verbatim later, so a reworded draft stops being file-ready. Done when the index carries a name, a path, and a summary for every proposal step 2 drafted, gives the count, and that instruction is the last thing said.

Keep looking

Skills are one crate of 608,666. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.