Repository navigation
planning: interview restate, wayfind absorb, stress test per mode #7586
Description
Parent
Refs #7555. Source: PLAN Phase 18, topic poteto-review. Thread: planning.
Depends on
- config-cascade: settings resolution and convention home #7571 Settings resolution and convention home
- skill-quality: skill authoring, quality and catalog #7582 Skill authoring, quality and catalog (final plugin shape before the devils-advocate eval)
Outcome
/planning:interview gains a restate action that waits for a yes and closes Matt's grilling
gaps; /planning:wayfind absorbs Matt's wayfinder; the stress-test setting is keyed per mode and
settled by an eval.
Decisions
/planning:interview: a "because" on the goal, a run-it-to-settle-it step, the quality bar when
the user can't judge; warn against nodding along; cross-check stated facts against code; route
"document my repo" to curate-language (D5, D69, Q72). Origin: Matt's grilling.- Interview
restateaction: one paragraph (goal, problem, done), waits for a yes in interactive
sessions (D104, Q130, Q131, Q170; fixed floor; Matt's). - feat(planning): every interview question opens with the context that drives the decision, with links to verify it #7475 and feat(planning): interview pairs every code with its plain name at every use #7480; one-question-at-a-time as a user setting; probe topics as prose in the planning
convention; offer/planning:audit-answersafter two accept-all rounds (setting, 0 = never);
end-of-round index table dropped (D69, D78, Q70, Q71, Q73, Q517). /planning:wayfindabsorbs Matt's wayfinder and reports every conflict: interview is the entry;
chart runs the interview inline; map closes to prd, decompose, work; single-session efforts skip the
map; destination confirmed first; setting research auto-startauto(D5, D108, Q205, Q531, Q532).
Wayfind accept items per Q523. Setting: wayfind HITL concurrency 1; suggestion threshold to be
measured./planning:devils-advocatestays in planning;plan_stress_testkeyed per mode (plan, proposal,
incumbent) (D103, Q164).plan-reviewerstays on, configurable (Q166; ours).- Type rules move from
/planning:designto a type-rules convention synced into plugins (Q12). - Research tags: devils-advocate eval (12 plans, 3 arms, 3 runs) after the plugin shape is final
settles theplan_stress_testdefault (Q165); hand-off phrasing eval (Q188); eval variance checked
on the first run (assumption 10).
Key interfaces
From the design's module layout: "planning: /planning:interview gains restate;
/planning:wayfind absorbs Matt's wayfinder; /planning:devils-advocate stays; plan-reviewer
stays on. Type rules leave /planning:design for a type-rules convention synced into plugins."
Settings: "Offer answer audit after 2 accept-all rounds (0 = never). ... plan_stress_test per mode;
plan-reviewer on." "Research auto-start auto; wayfind HITL concurrency 1."
Slices, filed when this phase starts: interview-and-restate, wayfind-absorb,
stress-test-per-mode-and-eval, type-rules-convention.
Done when
-
bash plugins/skill-quality/scripts/check-skill.sh plugins/planning/skillsexits 0, and the
interview skill has arestateaction file (noactions/directory on main). - The devils-advocate eval slice carries a
Probe result:comment before the default changes. - Every slice sub-issue is closed by a merged PR.
Out of scope
- Decompose and work-items changes (work-items thread).
Related
- fix(planning): interview page wrap-up friction: stale closed question, id count confusion, ops re-apply, restate cap #5893 interview wrap-up friction (sub-issue of this thread).
- feat(planning): interview questions must be self-contained, with an agreed terminology matrix and references #6136 self-contained interview questions (sub-issue of this thread).
- feat(planning): every interview question opens with the context that drives the decision, with links to verify it #7475 interview questions open with their context (sub-issue of this thread).
- feat(planning): interview pairs every code with its plain name at every use #7480 interview pairs every code with its plain name (sub-issue of this thread).
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: #7571, #7582
I read this as the planning-thread phase that adds a
restateaction to/planning:interview, folds the wayfinder into/planning:wayfind, and keysplan_stress_testper mode (plan, proposal, incumbent). The default forplan_stress_testis to be set by the devils-advocate eval. It also moves the type rules into a synced convention.The decisions and done-when items are specific, so I'm asking no questions. The work spans four slices (interview-and-restate, wayfind-absorb, stress-test-per-mode-and-eval, type-rules-convention), so it needs splitting into sub-issues before admission. The blocked-by line comes from the body's "Depends on" list. I couldn't confirm whether those two issues are still open. I found no likely duplicates.
Automated triage, applied by the lanes App.
2 remaining items
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).
melodic-automation-lanes commentedon Oct 24, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.kyle-sexton commentedon Oct 26, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.