A preserved method from https://github.com/mattpocock/skills at 3cca18b368ae, path skills/engineering/grill-with-docs, MIT. 22 of 12 source lines differ (183%), every difference claimed by an entry of the ledger with its reason. Entries: baseline-copies-2026-09-11, pull-2026-09-11, fold-2026-09-11, fold-walk-2026-09-11, vocabulary-owner-2026-09-12.
greenline renders its own frontmatter: quoted name and description, the description from the manifest override where one existed, no upstream activation flag
name: grill-with-docs
name: "grill-with-docs"
description: A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
description: "A relentless interview that shapes an initiative and records each settled ruling in the initiative's decisions.md. Use when a shaping conversation must outlive the session."
disable-model-invocation: true
---
---
lifecyclechangedvocabulary-owner-2026-09-12
upstream's one-line body: the scope paragraph, the native skill mechanism, the decisions.md recording and the handoff, which now also creates the initiative directory and initiative.md at shaping when none exists (carried from fold-walk-2026-09-11; the word operator became owner where the copy names the workspace's person, and request owner became request holder (the internal refactor's step 1, ruling 10, 2026-09-12))
Call the Skill tool twice, for "grilling" and "domain-modeling".
grill-with-docs fires when a larger intent needs shaping decisions that must outlive the session: it shapes the initiative and records every settled ruling in that initiative's `decisions.md`. Resolve the intended initiative from the request and the current work first, then read its intent, its existing decisions and the decisions book, `.greenline/DECISIONS.md`, when it exists; ask only when ownership stays ambiguous, and never reopen a ruling already recorded. It never manufactures a planning layer for a settled compact fix, which goes to implement as one ticket; a new component's open engineering choices belong to groundwork; a discussion that needs no durable record is grilling alone, which writes nothing to the repository.
Load both methods, grilling and domain-modeling, through the harness's native skill mechanism; when it has none, read each installed SKILL.md and its required support files.
Record each settled ruling in the initiative's `decisions.md` (`id: INIT-NNN/DEC`, `type: decisions`) as it lands, `status: draft` while questions stay open and `status: complete` when the frontier is empty; a question still open stays visible there rather than silently assumed. The initiative advances to decided only then. A ruling that outlives the initiative is promoted into the decisions book with a reference back to its entry. Stop at the planning boundary the owner set; the finished decisions are what to-spec reads.
## Handoff
Consumes: the initiative's intent (a request, or an accepted what-to-build proposal) and its existing decisions.md (INIT-NNN/DEC) when one exists
Produces: the initiative directory and its initiative.md (INIT-NNN) at shaping when none exists; the initiative's decisions.md (INIT-NNN/DEC), status draft then complete; the initiative advances to decided
Next: to-spec reads decisions.md
agents/openai.yaml
harnessremoved filebaseline-copies-2026-09-11
the renderer generates agents/openai.yaml from the manifest; the vendored copy is not projected
interface:
display_name: "Grill with Docs"
short_description: "Grill a design and write its docs"
policy:
allow_implicit_invocation: false
The timeline
Each entry that touched this method, with the differences it claimed as they stood at its commit, read from the repository's history.
2026-09-11baseline-copies-2026-09-11
the cutover to an edited copy (ADR 0039): the composed output written as the copy, every difference from upstream claimed with the reason of the overlay that produced it
SKILL.md
harnesschangedbaseline-copies-2026-09-11
greenline renders its own frontmatter: quoted name and description, the description from the manifest override where one existed, no upstream activation flag
name: grill-with-docs
name: "grill-with-docs"
description: A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
description: "A relentless interview that shapes an initiative and records each settled ruling in the initiative's decisions.md. Use when a shaping conversation must outlive the session."
disable-model-invocation: true
lifecyclechangedbaseline-copies-2026-09-11
greenline prelude, to fold: resolve the intended initiative from current work before asking; no planning layer for a settled compact fix; the Skill-tool call is the harness's native mechanism
**greenline prelude: current artifacts before questions.** Resolve the intended initiative from the request and current work, then read its intent and existing decisions. Ask only if ownership remains ambiguous. Use the method below to record substantive choices, not to manufacture a planning layer for a settled compact fix. A new component's open engineering choices use groundwork within the request loop; lasting choices follow the decisions-book contract in `.greenline/WORK.md`, with links from the work.
Where the body says “Call the Skill tool,” use the harness's native skill
mechanism; if none exists, read the named installed skill's SKILL.md and its
required support files. “Twice” means load both named methods. Carry this
translation into any delegated brief; it does not require a tool with that name.
lifecyclechangedbaseline-copies-2026-09-11
greenline completion, to fold: the decisions artifact and meaning revisions follow .greenline/WORK.md; pure discussion creates no repository records
## greenline completion: decisions.md
Follow `.greenline/WORK.md` for the initiative's decisions artifact and meaning revisions, and the shared ledger guide for this contributor's source use. Record settled choices as they become clear; incomplete questions stay visible. The initiative becomes decided only when its needed decisions are resolved. Return to the same request owner to continue the authorized work or stop at the operator's requested planning boundary. Pure discussion does not create repository records.
agents/openai.yaml
harnessremoved filebaseline-copies-2026-09-11
the renderer generates agents/openai.yaml from the manifest; the vendored copy is not projected
interface:
display_name: "Grill with Docs"
short_description: "Grill a design and write its docs"
policy:
allow_implicit_invocation: false
2026-09-11pull-2026-09-11
pin advance to 3cca18b: upstream moved with no change under the vendored paths
2026-09-11fold-2026-09-11
The fold: the prelude and completion bookends dissolve into upstream's one-line body, which now names the initiative, the harness's native skill mechanism, decisions.md and the handoff to to-spec.
2026-09-11fold-walk-2026-09-11
the coherence walk: the initiative's own record has a writer
SKILL.md
lifecyclechangedfold-walk-2026-09-11
upstream's one-line body: the scope paragraph, the native skill mechanism, the decisions.md recording and the handoff, which now also creates the initiative directory and initiative.md at shaping when none exists
Call the Skill tool twice, for "grilling" and "domain-modeling".
grill-with-docs fires when a larger intent needs shaping decisions that must outlive the session: it shapes the initiative and records every settled ruling in that initiative's `decisions.md`. Resolve the intended initiative from the request and the current work first, then read its intent, its existing decisions and the decisions book, `.greenline/DECISIONS.md`, when it exists; ask only when ownership stays ambiguous, and never reopen a ruling already recorded. It never manufactures a planning layer for a settled compact fix, which goes to implement as one ticket; a new component's open engineering choices belong to groundwork; a discussion that needs no durable record is grilling alone, which writes nothing to the repository.
Load both methods, grilling and domain-modeling, through the harness's native skill mechanism; when it has none, read each installed SKILL.md and its required support files.
Record each settled ruling in the initiative's `decisions.md` (`id: INIT-NNN/DEC`, `type: decisions`) as it lands, `status: draft` while questions stay open and `status: complete` when the frontier is empty; a question still open stays visible there rather than silently assumed. The initiative advances to decided only then. A ruling that outlives the initiative is promoted into the decisions book with a reference back to its entry. Stop at the planning boundary the operator set; the finished decisions are what to-spec reads.
## Handoff
Consumes: the initiative's intent (a request, or an accepted what-to-build proposal) and its existing decisions.md (INIT-NNN/DEC) when one exists
Produces: the initiative directory and its initiative.md (INIT-NNN) at shaping when none exists; the initiative's decisions.md (INIT-NNN/DEC), status draft then complete; the initiative advances to decided
Next: to-spec reads decisions.md
2026-09-12vocabulary-owner-2026-09-12
The workspace's person is the owner: the word operator became owner where the copy names the workspace's person, and request owner became request holder (the internal refactor's step 1, ruling 10, 2026-09-12); every earlier claim on a re-measured hunk is carried forward under its own kind, with its authority where it had one.
SKILL.md
lifecyclechangedvocabulary-owner-2026-09-12
upstream's one-line body: the scope paragraph, the native skill mechanism, the decisions.md recording and the handoff, which now also creates the initiative directory and initiative.md at shaping when none exists (carried from fold-walk-2026-09-11; the word operator became owner where the copy names the workspace's person, and request owner became request holder (the internal refactor's step 1, ruling 10, 2026-09-12))
Call the Skill tool twice, for "grilling" and "domain-modeling".
grill-with-docs fires when a larger intent needs shaping decisions that must outlive the session: it shapes the initiative and records every settled ruling in that initiative's `decisions.md`. Resolve the intended initiative from the request and the current work first, then read its intent, its existing decisions and the decisions book, `.greenline/DECISIONS.md`, when it exists; ask only when ownership stays ambiguous, and never reopen a ruling already recorded. It never manufactures a planning layer for a settled compact fix, which goes to implement as one ticket; a new component's open engineering choices belong to groundwork; a discussion that needs no durable record is grilling alone, which writes nothing to the repository.
Load both methods, grilling and domain-modeling, through the harness's native skill mechanism; when it has none, read each installed SKILL.md and its required support files.
Record each settled ruling in the initiative's `decisions.md` (`id: INIT-NNN/DEC`, `type: decisions`) as it lands, `status: draft` while questions stay open and `status: complete` when the frontier is empty; a question still open stays visible there rather than silently assumed. The initiative advances to decided only then. A ruling that outlives the initiative is promoted into the decisions book with a reference back to its entry. Stop at the planning boundary the owner set; the finished decisions are what to-spec reads.
## Handoff
Consumes: the initiative's intent (a request, or an accepted what-to-build proposal) and its existing decisions.md (INIT-NNN/DEC) when one exists
Produces: the initiative directory and its initiative.md (INIT-NNN) at shaping when none exists; the initiative's decisions.md (INIT-NNN/DEC), status draft then complete; the initiative advances to decided