kenoxa/do-design

Compose run-discuss (design scope) + run-advise + run-council + optional run-explore. User feedback loop with re-dispatch cap.

Phases

| # | Phase | Type | Skills | |---|-------|------|--------| | 1 | Intake | R — mainthread + conditional /run-discuss | /run-discuss (scope=design) | | 2 | Advise | C — invoke /run-advise then /run-council | /run-advise, /run-council | | 3 | Validate | G — invoke on demand | /run-explore | | 4 | Decide | mainthread | — |

Phase Trace: verify rows for intake, advise, validate, decide before STOP.

1. Intake

Accept: frame_artifact from /do-frame, freeform problem statement, or user pushback from prior round.

• With frame_artifact: extract constraints and blast-radius. Skip run-discuss when >= 3 concrete constraints.
• Thin input (fewer than 3 constraints): invoke /run-discuss with scope: design, goal from user input.
• Re-dispatch: invoke /run-discuss to drill into why the user resists before re-running advisory.

Session: reuse from /do-frame when carrying frame_artifact; generate otherwise.

2. Advise

MANDATORY — always invoke /run-advise then /run-council, in that order. No zero-dispatch exception for either; advisory is never self-contained at this phase.

Step 1 — run-advise: Invoke /run-advise with problem context, constraints from frame_artifact or discuss_artifact, and {source_artifact_path} set to the persisted authoritative artifact for this phase (typically the frame_artifact or discuss_artifact file under .scratch/<session>/). Returns advise_artifact.

Step 2 — run-council: Immediately after run-advise returns, invoke /run-council with:

• {advise_synthesis_path} = .scratch/<session>/advise-synthesis.md
• {source_artifact_path} = same path used for run-advise dispatch

Returns council_artifact (path to .scratch/<session>/council-synthesis.md).

Both advise_artifact and council_artifact are available for Phase 4 (Decide).

3. Validate

When advisory surfaces assumptions about codebase state, invoke /run-explore for feasibility probes. Feed results back into advisory context.

Zero-dispatch when advisory is self-contained — log with justification. (Zero-dispatch applies to Phase 3 only, never Phase 2.)

4. User Decision Gate

Assemble design_artifact per design-artifact.md from advise_artifact + council_artifact + frame_artifact. Write to .scratch/<session>/design-artifact.md.

When council-synthesis.md recommendation diverges from advise-synthesis.md recommendation: surface as a flagged divergence in the design_artifact Open Questions section for explicit user decision at this gate. No automatic precedence rule — do not auto-resolve.

Before presenting: scan for [DIVERGENCE], [CONFLICT], ${LETTER}-${kebab}, V__/R__ labels — rewrite each as plain English. Self-test: user must not need advise-synthesis.md to understand any question.

Present to user — direction and delivery slicing reviewed together. Main thread = sole decision authority.

| User action | Response | |------------|----------| | Approves | Suggest /do-build. STOP. | | Pushes back | Return to Intake with /run-discuss to refine, then re-dispatch /run-advise | | Rejects | Redirect to /do-frame. STOP. |

STOP after presenting. Never auto-forward. Cap: 3 re-dispatch rounds; surface stall after cap.

Anti-Patterns

• Auto-forwarding to /do-build without user approval
• Resolving model disagreements silently — divergence is signal, surface it
• Producing per-file implementation plans — that is /do-build's scope phase job
• Bypassing run-advise to dispatch agents directly
• Skipping run-advise as "zero-dispatch" — zero-dispatch only applies to Phase 3 (Validate)
• Re-dispatching full advisory batch when run-discuss could resolve pushback locally
• Ignoring frame_artifact constraints — carry all constraints into run-advise dispatch
• "I already know the right approach, skip advisory" — single-perspective answers miss tradeoffs; dispatch is mandatory
• "The user approved the direction, go build" — approval must be explicit; silence is not consent
• "Consultants agree, so skip validation" — convergence on wrong assumptions is still wrong; probe when evidence is thin
• Proceeding to Phase 4 without invoking run-council after run-advise — both steps are mandatory in Phase 2; run-council handles its own skip internally

Completion

• Phase Trace has rows for intake, advise, validate, decide [E3]
• design_artifact written to .scratch/<session>/ with delivery slices + constraints [E2]
• User explicitly approved or pushed back — no auto-forward [E2]