skills(brainstorming): make request-only, not auto-trigger
Upstream description ("You MUST use this before any creative work...") would
auto-fire the brainstorming skill on routine feature/code work. Rewrote the
frontmatter description to invoke ONLY when the user explicitly asks to
brainstorm/design. Methodology body (incl. HARD-GATE) unchanged. Noted in SOURCE.md.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -10,6 +10,7 @@ Harvested from obra/superpowers (MIT, Copyright (c) 2025 Jesse Vincent) at commi
|
||||
- No emojis were present in the source.
|
||||
- Added a `NOTE (ClaudeTools)` block near the top recording that the optional visual brainstorming server was intentionally omitted and that this is imported as a methodology reference.
|
||||
- No content was otherwise reworded; the brainstorming methodology is preserved as in the source apart from the normalization and the added note.
|
||||
- **Trigger changed (ClaudeTools, 2026-06-17):** the upstream `description` ("You MUST use this before any creative work...") auto-fired on routine feature/code work. Rewrote it to **request-only** - the skill now invokes only when the user explicitly asks to brainstorm/design. The methodology body (incl. the HARD-GATE) is unchanged; it just no longer self-triggers.
|
||||
|
||||
## Omitted upstream tooling (intentional)
|
||||
The optional visual brainstorming companion/server was NOT imported. Specifically, none of the following were fetched or included:
|
||||
|
||||
Reference in New Issue
Block a user