# /grill-with-docs - grilling plus durable notes
Use this skill when the user wants the `/grilling` interview and also wants the settled decisions captured as durable documentation.
Start with the `/grilling` behavior:
- inspect repo context when it can answer a question;
- provide the recommended answer;
- ask exactly one question at a time;
- continue until the important branches of the design tree are resolved.
Documentation posture
Do not write files immediately. First clarify what kind of durable artifact the user wants, or recommend one when the answer is obvious.
Common chiefOS destinations:
| Situation | Artifact | |---|---| | Internal chiefOS architecture, workflow, prompt, automation, or data-model decision | `chiefOS-mgmt-docs/proposals/<topic>.md` or an ADR-style note under the most relevant existing chiefOS docs folder | | Customer delivery decision | Customer folder note under `customers/<Customer Name>/` only when the customer/project context is explicit | | Active project task or blocker surfaced during the interview | Route capture to `/project-manager` rather than writing an ad-hoc task doc | | Skill creation or edit rationale | Skill-local notes only if the repo already uses them; otherwise keep rationale in the commit message or a chiefOS proposal doc | | Shared vocabulary that affects future skills | A glossary section in the same proposal/ADR unless there is already an owned glossary file |
Follow `./references/dependencies/conversint-current/references/output-paths.md` for routing. Do not invent new top-level folders.
Documentation loop
As decisions settle, keep a running draft in the chat with these sections:
```markdown # [Decision or Design Name]
## Context ## Decision ## Alternatives Considered ## Consequences ## Open Questions ## Glossary ```
Only write or update files after the user has approved the destination and the current draft content.
Write gates
- If the work touches skill creation or skill edits, read `./references/dependencies/conversint-current/references/skill-authoring.md` before writing docs that prescribe skill behavior. - If the work touches active projects, read `./references/dependencies/conversint-current/references/active-projects.md` and the relevant project ledger before writing. - If the work touches Conversint strategy, services, pricing, capacity, or client-facing language, load the relevant org-bundle files and drift-check contradictions. - If an interview creates project next steps, route durable task capture through `/project-manager`; do not create a parallel task system.
Final response
End with:
- the last resolved decision;
- the file path written, if any;
- remaining open questions;
- the next owning skill or manual action.