plan-creating-project-planslisted

# Creating Project Plans ## Purpose This Skill provides comprehensive guidance for creating **structured project plans** in the plans/ directory. Plans follow standardized organization, naming conventions, and acceptance criteria patterns for executable, traceable project work. **When to use this Skill:** - Creating new project plans - Organizing backlog items - Converting ideas to structured plans - Writing Gherkin acceptance criteria - Structuring multi-phase projects - Moving plans through workflow stages ## Mandatory Pre-Write and Post-Write Grilling Before writing any plan content, resolve all open design decisions with the user via structured multiple-choice grilling (pre-write grill). After writing the plan, validate and stress-test it with the user the same way (post-write grill). Neither gate is optional. **HARD RULE — 2-4 options required**: Every grilling question MUST present **2-4 concrete, mutually exclusive options**. Each option MUST state its trade-off in one sentence. Exactly one option MUST be marked `(Recommended)` with a one-sentence rationale. Open-ended questions without options are FORBIDDEN. Resolve one decision per question; tightly coupled decisions may be batched in a single multi-question prompt. **Mechanism**: use the `AskUserQuestion` tool (or the harness's native interactive multiple-choice tool) first when available; fall back to inline markdown options when it is not. **Explore before asking**: read the relevant repo artifacts before