gstack-to-planlisted

# Bridge: gstack Plan → Superpowers writing-plans **Announce at start:** "I'm using the bridge:gstack-to-plan skill to transform the gstack plan into a Superpowers implementation plan." ## Purpose gstack produces strategic, reviewed plans (CEO / design / eng / DX reviewed). Superpowers `writing-plans` needs an execution-level spec: exact files, bite-sized tasks, test commands, verification steps. This skill bridges the gap. ## Step 1 — Locate the Source Plan Search in this priority order: 1. File path provided as args (if the user specified one) 2. `docs/plan.md` 3. `docs/spec.md` 4. `plan.md` 5. `spec.md` 6. Any `.md` under `docs/` modified most recently (`ls -t docs/*.md 2>/dev/null | head -1`) 7. Any `.md` under `.gstack/` (`ls -t .gstack/**/*.md 2>/dev/null | head -1`) Read the located file in full. If nothing is found, stop and ask the user to specify the plan file path. ## Step 2 — Extract Structured Information Parse the plan and extract: | Field | Where to look | |-------|--------------| | **Goal / problem statement** | Title, intro, executive summary | | **Success metrics** | Acceptance criteria, success criteria, definition of done | | **In-scope work** | Scope, features, deliverables | | **Out-of-scope** | Non-goals, explicitly excluded items | | **User / workflow** | Target user, use cases, user flows | | **Technical constraints** | Tech stack, language, framework, APIs, infra limits | | **Architecture decisions** | Architecture, design decisions, patter