refining-speclisted

# Refining Spec **Derived from gstack `/spec` phases 1–4.** Same interrogation discipline — different output: a **feature-level design spec** in the repo for `writing-plans`, not a single backlog issue. **Derived from superpowers `brainstorming` output shape.** Saves where `writing-plans` expects input. ## Overview Turn an **office-hours design** (product framing, wedge, approach) into a **technically grounded spec** for **writing-board-tasks**. **Announce at start:** "I'm using the refining-spec skill to refine the design into a writing-board-tasks-ready spec." **REQUIRED INPUT:** An office-hours design doc. Check in order: 1. `docs/gstack/designs/<feature-slug>-design.md` (repo copy — preferred) 2. `docs/superpowers/specs/<feature-slug>-design.md` (if already refined) 3. `~/.gstack/projects/<slug>/*-design-*.md` (gstack default — fallback) **Save refined spec to:** `docs/superpowers/specs/<feature-slug>-design.md` **Do NOT:** File a GitHub issue, run `writing-plans`, write code, or spawn agents. Those are later steps. ## When to use | Situation | Use this skill? | |-----------|-----------------| | After `/office-hours`, before `writing-board-tasks` | **Yes** — recommended refinement step | | After superpowers `brainstorming` (already in repo) | **Optional** — only if spec needs code-grounded tightening | | Ready for one GitHub issue, skip plan | **No** — use gstack `/spec` instead | | No design doc yet | **No** — run `/office-hours` or `brainstorming` first | ##