rogee/superpowers
1
0
Fork 0
mirror of https://github.com/obra/superpowers.git synced 2026-04-25 11:09:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

refactor: split emergent-patterns into focused problem-solving skills

Browse Source 
**Restructure:**
- Split detecting-emergent-patterns (216 lines) into 5 focused skills (~60 lines each)
- Move tracing-lineages to skills/research/ (better category fit)
- Create skills/problem-solving/ category

**New problem-solving skills:**
- simplification-cascades: Find one insight that eliminates multiple components
- collision-zone-thinking: Force unrelated concepts together for breakthroughs
- meta-pattern-recognition: Spot patterns in 3+ domains
- inversion-exercise: Flip assumptions to reveal alternatives
- scale-game: Test at extremes to find fundamental limits
- when-stuck: Dispatch skill that maps stuck-symptoms to techniques

**Improvements:**
- Symptom-based when_to_use (what you'd actually think/feel)
- Quick reference tables for rapid scanning
- Pattern-based triggers (not exact phrase matching)
- Cross-references from brainstorming for discoverability

Each skill now: scannable in 30 seconds, applicable immediately, focused on one technique.
This commit is contained in:
Jesse Vincent
2025-10-10 14:34:51 -07:00
parent e901534e9e
commit ec15b59c89
12 changed files with 412 additions and 225 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
skills/collaboration/brainstorming/SKILL.md
View File

@@ -30,13 +30,13 @@ digraph brainstorming_modes {
UNDERSTANDING -> EXPLORING [label="Have enough context to propose alternatives\n(gathered purpose, constraints, success criteria)"];
EXPLORING -> UNDERSTANDING [label="New constraints emerge\n(compliance, infrastructure, security, 'Oh I forgot to mention...')"];
EXPLORING -> UNDERSTANDING [label="Partner reveals new constraint\n(compliance requirement, infrastructure limit, security need, forgotten requirement)"];
EXPLORING -> DESIGNING [label="Approach selected and validated\n(partner chose an approach, have all critical constraints)"];
DESIGNING -> UNDERSTANDING [label="Fundamental gaps revealed during validation\n(missing constraints, assumptions questioned)"];
DESIGNING -> UNDERSTANDING [label="Partner reveals fundamental gap\n(missing critical constraint, core assumption questioned)"];
DESIGNING -> EXPLORING [label="Need to compare alternatives\n(trade-offs significant, partner asks 'what are the options?')"];
DESIGNING -> EXPLORING [label="Need to reconsider approach\n(trade-offs too significant, partner questions approach)"];
}
```
@@ -79,12 +79,14 @@ When your partner confirms (any affirmative response):
## Related Skills
**When stuck at any point:**
- Use skills/problem-solving/when-stuck to dispatch to right technique
**During EXPLORING mode:**
- When approaches have genuine trade-offs: skills/architecture/preserving-productive-tensions
- When stuck or seeking innovation: skills/architecture/detecting-emergent-patterns
**Before proposing changes:**
- Understand why current approach exists: skills/architecture/tracing-knowledge-lineages
**Before proposing changes to existing code:**
- Understand why it exists: skills/research/tracing-knowledge-lineages
## Remember

4
skills/collaboration/executing-plans/SKILL.md
View File

@@ -32,9 +32,9 @@ digraph executing_modes {
REVIEWING -> EXECUTING [label="Plan is sound, no concerns\n(created TodoWrite, ready to start first batch)"];
REVIEWING -> BLOCKED [label="Plan has issues that prevent starting\n(missing info, unclear instructions, dependencies)"];
REVIEWING -> BLOCKED [label="Plan has critical gaps\n(missing information, unclear instructions, unmet dependencies)"];
EXECUTING -> BLOCKED [label="Hit a blocker mid-batch\n(missing dependency, test fails, unclear instruction)"];
EXECUTING -> BLOCKED [label="Cannot proceed with current task\n(dependency missing, test failing, instruction unclear)"];
EXECUTING -> REPORTING [label="Batch completed successfully\n(all tasks done, verifications pass)"];