armelhbobdad/oh-my-skills / .claude/skills/bmad-brainstorming
bmad-brainstorming
VerifiedFacilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 254 B |
| brain-methods.csv | other | 15.9 KB |
| steps/step-01-session-setup.md | markdown | 7.3 KB |
| steps/step-01b-continue.md | markdown | 3.8 KB |
| steps/step-02a-user-selected.md | markdown | 7.4 KB |
| steps/step-02b-ai-recommended.md | markdown | 7.8 KB |
| steps/step-02c-random-selection.md | markdown | 7.6 KB |
| steps/step-02d-progressive-flow.md | markdown | 9.6 KB |
| steps/step-03-technique-execution.md | markdown | 16.3 KB |
| steps/step-04-idea-organization.md | markdown | 10.5 KB |
| template.md | markdown | 245 B |
| workflow.md | markdown | 2.7 KB |
steps/step-01b-continue.md
View on GitHub# Step 1b: Workflow Continuation
## MANDATORY EXECUTION RULES (READ FIRST):
- β
YOU ARE A CONTINUATION FACILITATOR, not a fresh starter
- π― RESPECT EXISTING WORKFLOW state and progress
- π UNDERSTAND PREVIOUS SESSION context and outcomes
- π SEAMLESSLY RESUME from where user left off
- π¬ MAINTAIN CONTINUITY in session flow and rapport
- β
YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
## EXECUTION PROTOCOLS:
- π― Load and analyze existing document thoroughly
- πΎ Update frontmatter with continuation state
- π Present current status and next options clearly
- π« FORBIDDEN repeating completed work or asking same questions
## CONTEXT BOUNDARIES:
- Existing document with frontmatter is available
- Previous steps completed indicate session progress
- Brain techniques CSV loaded when needed for remaining steps
- User may want to continue, modify, or restart
## YOUR TASK:
Analyze existing brainstorming session state and provide seamless continuation options.
## CONTINUATION SEQUENCE:
### 1. Analyze Existing Session
Load existing document and analyze current state:
**Document Analysis:**
- Read existing `{brainstorming_session_output_file}`
- Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals`
- Review content to understand session progress and outcomes
- Identify current stage and next logical steps
**Session Status Assessment:**
"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
**Current Session Status:**
- **Steps Completed:** [List completed steps]
- **Techniques Used:** [List techniques from frontmatter]
- **Ideas Generated:** [Number from frontmatter]
- **Current Stage:** [Assess where they left off]
**Session Progress:**
[Brief summary of what was accomplished and what remains]"
### 2. Present Continuation Options
Based on session analysis, provide appropriate options:
**If Session Completed:**
"Your brainstorming session appears to be complete!
**Options:**
[1] Review Results - Go through your documented ideas and insights
[2] Start New Session - Begin brainstorming on a new topic
[3] Extend Session - Add more techniques or explore new angles"
**HALT β wait for user selection before proceeding.**
**If Session In Progress:**
"Let's continue where we left off!
**Current Progress:**
[Description of current stage and accomplishments]
**Next Steps:**
[Continue with appropriate next step based on workflow state]"
### 3. Handle User Choice
Route to appropriate next step based on selection:
**Review Results:** Load appropriate review/navigation step
**New Session:** Start fresh workflow initialization
**Extend Session:** Continue with next technique or phase
**Continue Progress:** Resume from current workflow step
### 4. Update Session State
Update frontmatter to reflect continuation:
```yaml
---
stepsCompleted: [existing_steps]
session_continued: true
continuation_date: { { current_date } }
---
```
## SUCCESS METRICS:
β
Existing session state accurately analyzed and understood
β
Seamless continuation without loss of context or rapport
β
Appropriate continuation options presented based on progress
β
User choice properly routed to next workflow step
β
Session continuity maintained throughout interaction
## FAILURE MODES:
β Not properly analyzing existing document state
β Asking user to repeat information already provided
β Losing continuity in session flow or context
β Not providing appropriate continuation options
## CONTINUATION PROTOCOLS:
- Always acknowledge previous work and progress
- Maintain established rapport and session dynamics
- Build upon existing ideas and insights rather than starting over
- Respect user's time by avoiding repetitive questions
## NEXT STEP:
Route to appropriate workflow step based on user's continuation choice and current session state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |