fix(idea-refine): drop the orphaned Trigger Phrases label, add the boundary line

Applies the two review suggestions on #624: the label was left with nothing
under it once the phrases moved to When to Use, and the Not-for line (from
nucliweb's review, originally in #492) marks where interview-me and
spec-driven-development take over.

Co-authored-by: Joan León <nucliweb@users.noreply.github.com>
This commit is contained in:
Addy OsmaniandJoan León committed 2026-10-13 16:15:50 -04:00
1 parent 8ed851127c
commit f3400940f6
1 file changed
+1 -1
+1 -1
View File
@@ -15,6 +15,7 @@ Refines raw ideas into sharp, actionable concepts worth building through structu
- Use when you need to stress-test assumptions before committing to a direction
- Use when you want to expand options before converging on one
- Trigger phrases: "Help me refine this idea", "Ideate on [concept]", "Stress-test my plan"
- Not for: a user who is unsure what they want at all (use `interview-me`), or a direction already chosen that needs a spec (use `spec-driven-development`)
## How It Works
@@ -31,7 +32,6 @@ This skill is primarily an interactive dialogue. Invoke it with an idea, and the
bash skills/idea-refine/scripts/idea-refine.sh
```
**Trigger Phrases:**
## Output
The final output is a markdown one-pager saved to `docs/ideas/[idea-name].md` (after user confirmation), containing: