mirror of
https://github.com/obra/superpowers.git
synced 2026-06-09 17:02:07 +00:00
5 lines
12 KiB
Plaintext
5 lines
12 KiB
Plaintext
|
b0VIM 9.1 h<><68>hЭM<0E><> jesse m4.local ~jesse/.claude/skills/brainstorming/SKILL.md utf-8
3210 #"! U
|
|||
|
|
<00>
|
|||
|
|
O
|
|||
|
|
|
|||
|
|
<00> <00> <00> <00> S R <00> <00> f e C B <00> t <00> <00> <00> <00> ~ f <00> <00> <00> <00> Z A <00> <00> <00> X - Annou- An- Announce skill us- Announce skill usa- Announce skill usage at start - - Announce skill usage at start - Go backward when needed - flexibility > rigid progression - Present incrementally, validate as you go - Explore 2-3 alternatives before settling - Apply YAGNI ruthlessly - One question per message during Phase 1 ## Remember - Understand why it exists: skills/research/tracing-knowledge-lineages **Before proposing changes to existing code:** - When approaches have genuine trade-offs: skills/architecture/preserving-productive-tensions **During exploration:** ## Related Skills **Don't force forward linearly** when going backward would give better results. - Something doesn't make sense → Go back and clarify - Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives - Validation shows fundamental gap in requirements → Return to Phase 1 - Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it **You can and should go backward when:** ## When to Revisit Earlier Phases - Create detailed plan in the worktree - Switch to skills/collaboration/writing-plans skill - Announce: "I'm using the Writing Plans skill to create the implementation plan." When your human partner confirms (any affirmative response): Ask: "Ready to create the implementation plan?" ### Phase 5: Planning Handoff - Return here when worktree ready - Follow that skill's process for directory selection, safety verification, and setup - Switch to skills/collaboration/using-git-worktrees - Announce: "I'm using the Using Git Worktrees skill to set up an isolated workspace." When design is approved and implementation will follow: ### Phase 4: Worktree Setup (for implementation) - Ask after each section: "Does this look right so far?" - Cover: Architecture, components, data flow, error handling, testing - Present in 200-300 word sections ### Phase 3: Design Presentation - Ask your human partner which approach resonates - For each: Core architecture, trade-offs, complexity assessment - Propose 2-3 different approaches ### Phase 2: Exploration - Gather: Purpose, constraints, success criteria - Prefer multiple choice when possible - Ask ONE question at a time to refine the idea - Check current project state in working directory ### Phase 1: Understanding ## The Process **Announce at start:** "I'm using the Brainstorming skill to refine your idea into a design." **Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation. Transform rough ideas into fully-formed designs through structured questioning and alternative exploration. ## Overview # Brainstorming Ideas Into Designs --- description: IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation name: Brainstorming ---
|