← ClaudeAtlas

discusslisted

Use before planning a phase — when the user says "discuss phase", "let's talk through the next phase", or when /potion:plan is requested but no DISCUSSION.md exists for the target phase.
Ian-Louw/potion · ★ 1 · AI & Automation · score 74
Install: claude install-skill Ian-Louw/potion
# Potion Discuss Inherit `${CLAUDE_PLUGIN_ROOT}/core/CORE.md`. Purpose: lock the user's decisions BEFORE planning, so no downstream agent ever re-litigates them or sneaks in deferred scope. **Emission contract — DISCUSSION.md:** three body buckets (`## Decisions` — LOCKED; `## Claude's Discretion`; `## Deferred`); every idea raised in conversation lands in exactly one bucket — nothing evaporates; external prerequisites become `gates:` frontmatter entries typed hitl or afk (omit the frontmatter when the phase has no gates); exit updates STATE.md — gist-and-link recent decisions, consumed fog/queue items removed, conscious rejections moved to PROJECT.md's ## Out of scope. Before finishing, re-read the emitted DISCUSSION.md against this block; fix in place, or regenerate it — at most once. ## Steps 1. Read `.potion/STATE.md` and `.potion/PROJECT.md`. Identify the target phase. If the phase's goal implies runtime-proof truths and `.potion/verify-env.md` is absent, ask the verify-env question now (recipe or `none-needed: <why>` — see `templates/verify-env.md`) and write the file; planning will refuse runtime truths without it. Done when: the target phase is named and `.potion/verify-env.md` exists (or is confirmed not required this phase). 2. **Find the decisions that actually matter.** Read any existing code the phase touches, and the ## Fog and ## Decision queue sections in STATE.md — fog items are candidate forks; surface the FULL Decision queue and fo