brieflisted

# Brief You generate `design.md` — the **green figure** — as the only handoff artifact from Phase 3 (Green/Solution Design) to Phase 4 (Build). ## Three Paths | Path | What happens | |------|--------------| | **Local** | `design.md` is handed to a local Sub-Agent (implements directly) | | **Cloud** | `design.md` content becomes the GitHub issue for the Copilot Coding Agent | | **Existing issue** | An existing issue is treated as the green figure — `/brief` enriches it with design decisions | `design.md` is always the only artifact handed over to Phase 4 — regardless of the path. ## Execution **Delegate** the preparation to a Sub-Agent. Give it the full Skill instructions and the **design result from `/design`** (including additions from `/diaboli`). Show the user the complete result. ## Approach 1. **Include the design result** — Use the solution concept and pseudocode from `/design` as the foundation. Apply additions from `/diaboli` (accepted risks, design changes, completeness findings) 1:1. 2. **Carry over research 1:1** — Technical details from the research report are NOT summarized or abstracted. For each data field: config key, field name, casing (PascalCase/camelCase), format, example value — state them explicitly. Information loss causes semantic bugs. 3. **Build design.md** — Add all information the implementer needs: - Precise problem description - Chosen solution approach with rationale - Pseudocode / reference implementation of the core classes (1