Context
Filed by course lane 5 (#2903) after a /planning:audit-answers adversarial pass (two fresh-context validators, upstream primaries fetched independently) challenged the lane's zero-work-items answer. Two upstream grilling-family techniques are absent from planning:interview:
- Ungrillable-question → prototype detour (both validators, grep-confirmed absent): upstream fires it mid-grilling — "stop grilling. Build the throwaway version with prototype, look at it, then come back and answer in one line" (
docs/productivity/grill-me.md; also the routing table in docs/productivity/grilling.md). Our route exists only downstream (planning:wayfind prototype items, planning:plan build-technique selection, planning:brainstorm); the interview's mid-session composition names research/exploration/handoff only, and its categorization taxonomy (resolvable / blocked / defer-with-assumption / defer-fully) has no needs-an-artifact-to-react-to arm.
- Plan-mode-off while interviewing (validator dissent resolved by the human to adopt): beyond upstream's taste point ("Plan mode primes the agent to rush toward producing a plan"), our skill has a mechanical edge — the ask-time open-question register write is load-bearing, and plan mode's read-only enforcement blocks it.
Proposed work
- Add a prototype arm to the interview: one line in "Mid-interview composition" (route an ungrillable look/feel/behavior question to
prototype:explore-directions / prototype:pressure-test if installed, return, answer in one line) and one arm in context/loop.md's categorization taxonomy
- Add the plan-mode gotcha line (leave plan mode off while interviewing; the register write is blocked under read-only enforcement)
- Reconcile
planning:plan "Plan Mode Integration"'s clarifying-rounds-in-plan-mode sentence with the lane 4 asset-rush doctrine (route substantive rounds to the interview outside plan mode; keep plan-mode rounds to scoping confirms)
- planning version bump + CHANGELOG
Acceptance criteria
References
docs/upstream/aihero-core-lanes.md (lane 5 rows + audit record)- Upstream:
mattpocock/skills docs/productivity/grill-me.md §"Grillable and ungrillable", docs/productivity/grilling.md routing table
Metadata
| Field |
Value |
| Category |
unspecified |
| Area |
planning |
| Ecosystem |
unspecified |
Context
Filed by course lane 5 (#2903) after a
/planning:audit-answersadversarial pass (two fresh-context validators, upstream primaries fetched independently) challenged the lane's zero-work-items answer. Two upstream grilling-family techniques are absent fromplanning:interview:docs/productivity/grill-me.md; also the routing table indocs/productivity/grilling.md). Our route exists only downstream (planning:wayfindprototype items,planning:planbuild-technique selection,planning:brainstorm); the interview's mid-session composition names research/exploration/handoff only, and its categorization taxonomy (resolvable / blocked / defer-with-assumption / defer-fully) has no needs-an-artifact-to-react-to arm.Proposed work
prototype:explore-directions/prototype:pressure-testif installed, return, answer in one line) and one arm incontext/loop.md's categorization taxonomyplanning:plan"Plan Mode Integration"'s clarifying-rounds-in-plan-mode sentence with the lane 4 asset-rush doctrine (route substantive rounds to the interview outside plan mode; keep plan-mode rounds to scoping confirms)Acceptance criteria
plan/SKILL.mdtension reconciled — settled by the diffdocs/upstream/aihero-core-lanes.mdupdated with the merged pointerReferences
docs/upstream/aihero-core-lanes.md(lane 5 rows + audit record)mattpocock/skillsdocs/productivity/grill-me.md§"Grillable and ungrillable",docs/productivity/grilling.mdrouting tableMetadata