// Skips obvious branches inside grilling sessions by stating the assumed answer and moving on. Use when the user says fast-forward, skip, obvious, same as me, or next unclear area.
Creates or revises one portable agent skill with concise routing, progressive disclosure, and clear safety boundaries. Use when the user wants to write, clean up, or restructure a skill.
Finds Codex session coordinates by id, title, repo path, rollout path, or topic. Use when a user or another skill needs thread metadata and rollout paths for its own review.
Reviews recent Codex sessions for repeated agent failures and skill improvements. Use for daily/weekly retrospectives, skill audits, agent-pattern analysis, or cleanup recommendations.
Clarifies fuzzy direction into durable memory and issue-shaping handoff. Use when the user wants to turn an idea, conversation, ADR, PRD, or prior session into clear agent-ready work.
Gathers internal or external evidence for one decision and returns sourced patterns. Use when design, planning, retrospectives, or architecture depends on research before deciding.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates agent-owned documentation under `.agents/` inline as decisions crystallise. Use when the real task is defining purpose, scope, structure, canonical terms, capture/refinement criteria, or other durable decisions for the project.
| name | fast-forward |
| description | Skips obvious branches inside grilling sessions by stating the assumed answer and moving on. Use when the user says fast-forward, skip, obvious, same as me, or next unclear area. |
Use this as a companion maneuver inside grill-me or grill-with-docs.
When the user signals that the current line of questioning is obvious or low-value, do not end the grilling session. Instead:
Use this response shape:
Fast-forwarding this branch.
I am treating these assumptions as provisionally resolved:
- ...
- ...
Next unclear branch: ...
Question: ...
Keep the assumptions short. The goal is to remove boring detail, not create a new report.
grill-me, this only changes conversation flow.grill-with-docs, documentation still follows grill-with-docs rules..agents/CONTEXT.md or an ADR under .agents/adr/, ask for explicit confirmation before writing.Fast-forward branches where:
Do not fast-forward when:
User:
fast forward, this is obvious
Assistant:
Fast-forwarding this branch.
I am treating these assumptions as provisionally resolved:
- The hosted client remains the default.
- Embedded delivery is not part of the public API.
- Package-local opt-out is enough for now.
Next unclear branch: how feature discovery should be represented.
Question: should discovery use one shared endpoint or one endpoint per feature?