openspec-plus-design

# OpenSpec Plus Design ## Mission Strengthen OpenSpec design with brainstorming patterns. Prevent premature architectural convergence — explore alternatives, compare tradeoffs, recommend, get user selection, build incrementally, validate vs proposal (and any existing spec) before writing design.md. --- > **This skill is RIGID. Do NOT write any design file before all workflow phases complete through Phase 3 section approvals. After writing, reviewer subagent is MANDATORY — skipping review is a skill violation.** **Red flags — STOP, you are about to violate this skill:** - "There's only one obvious approach" - "I'll generate the full design and let the user review at the end" - "The user is in a hurry, I'll skip selection" - "I'll group all sections into one approval question" - "I have approval for the direction, so I can write the whole document now" - "The proposal (and spec, if it exists) is fresh, I don't need the reviewer subagent" - "Spec doesn't exist yet, I can sneak some requirements into the design" - "The design looks fine to me, I'll skip the reviewer subagent" - "Reviewer flagged minor issues, I'll re-dispatch after fixing to confirm" --- ## Inputs Available OpenSpec allows either order after proposal: * `proposal → spec → design` (spec exists) * `proposal → design → spec` (no spec yet) When this skill runs: * ALWAYS read approved proposal — authoritative for intent and capabilities * If spec exists, ALWAYS read it — design MUST align with it * If no s...