fix: require spec file before story generation — don't reinvent planning

skills/run/SKILL.md

@@ -46,13 +46,28 @@ Check if `.loop/prd.json` exists.
 
 **If it does NOT exist**, generate it:
 
-1. Search for existing specs:
+1. Search for existing specs or plans:
    - `docs/superpowers/specs/*.md`
+   - `docs/superpowers/plans/*.md`
    - `docs/specs/*.md`
-   - `SPEC.md`, `PRD.md`, `DESIGN.md` at project root
+   - `docs/plans/*.md`
+   - `SPEC.md`, `PRD.md`, `DESIGN.md`, `PLAN.md` at project root
+   - Any markdown file that looks like a feature spec or implementation plan
 
    If found: "I found a spec at `{path}`. Using it to generate stories."
-   If not found: ask "What do you want to build? 1-3 sentences."
+
+   If NOT found, stop and tell the user:
+
+   > **No spec or plan found.** Agent Loop decomposes existing plans into stories — it doesn't create plans from scratch.
+   >
+   > Create a plan first, then re-run `/agent-loop:run`:
+   > - Describe your idea to Claude and ask it to write a spec
+   > - Use `/plan` if available
+   > - Or create a markdown file at `docs/specs/` or `SPEC.md`
+   >
+   > The plan should describe what to build, the tech stack, and key requirements.
+
+   **STOP here. Do NOT ask the user to describe the project in a few sentences. Do NOT proceed without a spec file.**
 
 2. Read the project root and tech stack info.