From bc7a1e2f047c6ec2646ac33fa4e8ef0259163e55 Mon Sep 17 00:00:00 2001 From: Sheldon Finlay Date: Fri, 27 Mar 2026 15:08:30 -0400 Subject: [PATCH] =?UTF-8?q?fix:=20require=20spec=20file=20before=20story?= =?UTF-8?q?=20generation=20=E2=80=94=20don't=20reinvent=20planning?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- skills/run/SKILL.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/skills/run/SKILL.md b/skills/run/SKILL.md index 6c56499..78035b8 100644 --- a/skills/run/SKILL.md +++ b/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.