From pantheon
* **Description:** Initiates an interactive conversation between the developer and Zeus (the Orchestrator) to detail the system requirements, stack, linting sensors, and specific business rules. Supports brownfield mode when `.pantheon/SCAN.md` exists.
How this command is triggered — by the user, by Claude, or both
Slash command
/pantheon:discusspantheon/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Command: /pantheon:discuss ## 1. Overview * **Description:** Initiates an interactive conversation between the developer and Zeus (the Orchestrator) to detail the system requirements, stack, linting sensors, and specific business rules. Supports brownfield mode when `.pantheon/SCAN.md` exists. * **Responsible Agent:** Zeus * **Runtimes Target:** Claude Code, Codex ## 2. Pre-conditions * `.pantheon/config.json` must exist (workspace initialized via `/pantheon:init`). ## 3. Inputs * Developer prompts and instructions. * References to any initial designs or documents. * `.pantheon/SCAN.md...
.pantheon/SCAN.md exists..pantheon/config.json must exist (workspace initialized via /pantheon:init)..pantheon/SCAN.md (optional — triggers brownfield mode if present).Zeus checks if .pantheon/SCAN.md exists.
SCAN.md review gate: Before loading context, Zeus asks the developer:
SCAN.md found. Have you reviewed and corrected it before proceeding? (y/n)
.pantheon/SCAN.md, review all [INFERRED] items for accuracy, correct any misidentified modules or stack details, and re-run /pantheon:discuss after validation. Zeus halts.Context load: Zeus reads .pantheon/SCAN.md and opens the session with a summary:
SCAN.md found. Brownfield context loaded.
Auto-mapped:
stack → <Block 1: runtime>
lint → <Block 1: lint command or "none detected">
test → <Block 1: test command or "none detected">
modules → <Block 2: module list> (<N> total)
signals → <N> [RISK], <N> [GAP], <N> [INCONSISTENCY]
I'll confirm critical points and fill in what the scan couldn't answer.
Targeted interview: Zeus asks only the questions the scan could not answer with confidence:
[INFERRED] items Zeus is unsure about.Zeus does not re-ask about stack, dependencies, or sensor commands — these are already answered by SCAN.md.
Spec Drafting: Zeus merges SCAN.md context with developer answers and writes SPEC.md.
Validation: Zeus ensures all fields required by the spec template are populated.
SPEC.md: The official, complete specification document for the phase.npx claudepluginhub ederdomenici/pantheon --plugin pantheon/discussDebates implementation approaches by listing 3+ options with pros/cons/effort, comparing criteria, recommending one with reasoning and contingencies.
/discussConducts interactive Jobs-to-be-Done analysis, UX journey design, and requirements gathering for features, producing user stories and acceptance criteria.
/discussStarts or continues discussion on the current phase to build context before planning. Shows working directory, plugin root, and phase state.