roll-designlisted

# Design > Follows the Architecture Constraints, Development Discipline, and Engineering Common Sense defined in the project AGENTS.md. Discuss approaches, design architecture, plan requirements, and write to `.roll/backlog.md`. DDD modeling depth scales automatically with input scope. ## When to Use - Requirements or approach are uncertain and multiple options need to be compared - Requirements have not yet entered the backlog - A solution needs to be designed before splitting into Stories - An existing plan needs to be written into `.roll/backlog.md` > **Doc-refresh discipline**: When splitting stories that change user-visible behavior, always append a closing "doc-refresh" story. > **文档刷新纪律**：拆出的 story 只要改变了用户可见行为，最后必须追加一张"文档刷新"收尾 story。 > See [Doc Update Discipline](#doc-update-discipline) at the bottom of this file for the full rule. ## Use This Skill For - Approach exploration and comparison (discuss phase) - New project domain modeling (Event Storming → Context Map → Tactical Model) - New requirement planning with domain context - Solution design - Splitting into Stories - Creating US / FIX entries ## When Not to Use - One-liner capture of ideas or bugs (use `$roll-idea`) - Executing an already-split US-XXX (use `$roll-build`) - Fixing a well-defined FIX-XXX (use `$roll-fix`) ## Quick Start ```bash # New project from scratch → full DDD modeling $roll-design "design an e-commerce order system from scratch" # Approach is uncertain → discuss first, then plan $