decidelisted

# Decide A decision that lives only in conversation is a decision the next session will re-make. Capture it as a decision need in the spec — linked, validated, findable (ADR_0002). Standalone: no external tooling beyond the spec build. ## Workflow ### 1. Resolve configuration Read `[tool.patdhlk-skills]` from `ubproject.toml`; the `decision` role must be mapped (missing → `/setup-patdhlk-skills`). Target document: `decisions_doc` from the config when set; otherwise find where existing decision directives live (often `<spec_dir>/architecture/`), ask the user once, persist as `decisions_doc`. When the user names a topic page ("put it with the codegen decisions"), honor that for this call. ### 2. Extract the decision — interview for what's missing From the conversation, assemble: - **Title** — the decision as a verdict, not a topic ("Parser separated from codegen", not "Parser architecture"). - **Context** — the forces: what problem, which constraints. - **Decision** — what was chosen, concretely. - **Alternatives** — what was NOT chosen and why. *A decision without rejected alternatives is a description, not a decision* — if the conversation has none, ask for at least one. - **Consequences** — both directions: what gets better (✅), what is paid (❌). A consequences list with no ❌ is unfinished. Status: `accepted` for a settled decision (the normal case), `proposed` when the user marks it tentative. ### 3. Link it into the graph Build a fresh needs.json (ADR_000