Merge branch 'main' into refactor/code-review-sharded-dual-phase
This commit is contained in:
Alex Verkhovsky
GitHub
commit
a2458a5537
|
|
@ -1,89 +1,214 @@
|
|||
# Workflows
|
||||
|
||||
Workflows are structured processes that guide agents through complex tasks. Think of them as recipes that ensure consistent, high-quality outcomes.
|
||||
Workflows are like prompts on steroids. They harness the untapped power and control of LLMs through progressive disclosure—breaking complex tasks into focused steps that execute sequentially. Instead of random AI slop where you hope for the best, workflows give you repeatable, reliable, high-quality outputs.
|
||||
|
||||
## What is a Workflow?
|
||||
This guide explains what workflows are, why they're powerful, and how to think about designing them.
|
||||
|
||||
A workflow is a step-by-step process that agents follow to accomplish specific objectives. A workflow can be a single file if small enough, but more than likely is comprized of a very small workflow or skill definition file with multiple steps and data files that are loaded as needed on demand. Each step file:
|
||||
---
|
||||
|
||||
- Defines a clear goal
|
||||
- Provides instructions for the agent
|
||||
- May include decision points or user interactions
|
||||
- Produces specific outputs
|
||||
- Progressively at a specific point can load the next proper step.
|
||||
## What Is a Workflow?
|
||||
|
||||
A workflow is a structured process where the AI executes steps sequentially to accomplish a task. Each step has a specific purpose, and the AI moves through them methodically—whether that involves extensive collaboration or minimal user interaction.
|
||||
|
||||
Think of it this way: instead of asking "help me build a nutrition plan" and getting a generic response, a workflow guides you (or runs automatically) through discovery, assessment, strategy, shopping lists, and prep schedules—each step building on the last, nothing missed, no shortcuts taken.
|
||||
|
||||
## How do workflows differ from skills?
|
||||
|
||||
Actually they really do not - a workflow can be a skill, and a skill can be a workflow. The main thing with a BMad workflow is the suggestion to follow certain conventions, which actually are also skill best practices. A skill has a few optional and required fields to add as the main file workflow and get stored in a specific location depending on your tool choice for automatic invocation by the llm - whereas workflows are generally intentionally launched, with from another process calling them, or a user invoking via a slash command. In the near future, workflows will optionally be installable as skills also - but if you like, you can add front matter to your custom workflows based on the skill spec from Anthropic, and put them in the proper location your tool dictates.
|
||||
|
||||
### The Power of Progressive Disclosure
|
||||
|
||||
Here's why workflows work so well: the AI only sees the current step. It doesn't know about step 5 when it's on step 2. It can't get ahead of itself, skip steps, or lose focus. Each step gets the AI's full attention, completing fully before the next step loads.
|
||||
|
||||
This is the opposite of a giant prompt that tries to handle everything at once and inevitably misses details or loses coherence.
|
||||
|
||||
Workflows exist on a spectrum:
|
||||
|
||||
- **Interactive workflows** guide users through complex decisions via collaboration and facilitation
|
||||
- **Automated workflows** run with minimal user input, processing documents or executing tasks
|
||||
- **Hybrid workflows** combine both—some steps need user input, others run automatically
|
||||
|
||||
### Real-World Workflow Examples
|
||||
|
||||
**Tax Organizer Workflow**
|
||||
|
||||
A tax preparation workflow that helps users organize financial documents for tax filing. Runs in a single session, follows prescriptive IRS categories, produces a checklist of required documents with missing-item alerts. Sequential and compliance-focused.
|
||||
|
||||
**Meal Planning Workflow**
|
||||
|
||||
Creates personalized weekly meal plans through collaborative nutrition planning. Users can stop mid-session and return later because the workflow tracks progress. Intent-based conversation helps discover preferences rather than following a script. Multi-session, creative, and highly interactive.
|
||||
|
||||
**Course Creator Workflow**
|
||||
|
||||
Helps instructors design course syllabi. Branches based on course type—academic courses need accreditation sections, vocational courses need certification prep, self-paced courses need different structures entirely.
|
||||
|
||||
**Therapy Intake Workflow**
|
||||
|
||||
Guides mental health professionals through structured client intake sessions. Highly sensitive and confidential, uses intent-based questioning to build rapport while ensuring all required clinical information is collected. Continuable across multiple sessions.
|
||||
|
||||
**Software Architecture Workflow** (BMM Module)
|
||||
|
||||
Part of a larger software development pipeline. Runs after product requirements and UX design are complete, takes those documents as input, then collaboratively walks through technical decisions: system components, data flows, technology choices, architectural patterns. Produces an architecture document that implementation teams use to build consistently.
|
||||
|
||||
**Shard Document Workflow**
|
||||
|
||||
Nearly hands-off automated workflow. Takes a large document as input, uses a custom npx tool to split it into smaller files, deletes the original, then augments an index with content details so the LLM can efficiently find and reference specific sections later. Minimal user interaction—just specify the input document.
|
||||
|
||||
These examples show the range: from collaborative creative processes to automated batch jobs, workflows ensure completeness and consistency whether the work involves deep collaboration or minimal human oversight.
|
||||
|
||||
### The Facilitative Philosophy
|
||||
|
||||
When workflows involve users, they should be **facilitative, not directive**. The AI treats users as partners and domain experts, not as passive recipients of generated content.
|
||||
|
||||
**Collaborative dialogue, not command-response**: The AI and user work together throughout. The AI brings structured thinking, methodology, and technical knowledge. The user brings domain expertise, context, and judgment. Together they produce something better than either could alone.
|
||||
|
||||
**The user is the expert in their domain**: A nutrition planning workflow doesn't dictate meal plans—it guides users through discovering what works for their lifestyle. An architecture workflow doesn't tell architects what to build—it facilitates systematic decision-making so choices are explicit and consistent.
|
||||
|
||||
**Intent-based facilitation**: Workflows should describe goals and approaches, not scripts. Instead of "Ask: What is your age? Then ask: What is your goal weight?" use "Guide the user through understanding their health profile. Ask 1-2 questions at a time. Think about their responses before asking follow-ups. Probe to understand their actual needs."
|
||||
|
||||
The AI figures out exact wording and question order based on conversation context. This makes interactions feel natural and responsive rather than robotic and interrogative.
|
||||
|
||||
**When to be prescriptive**: Some workflows require exact scripts—medical intake, legal compliance, safety-critical procedures. But these are the exception, not the rule. Default to facilitative intent-based approaches unless compliance or regulation demands otherwise.
|
||||
|
||||
---
|
||||
|
||||
## Why Workflows Matter
|
||||
|
||||
Workflows solve three fundamental problems with AI interactions:
|
||||
|
||||
**Focus**: Each step contains only instructions for that phase. The AI sees one step at a time, preventing it from getting ahead of itself or losing focus.
|
||||
|
||||
**Continuity**: Workflows can span multiple sessions. Stop mid-workflow and return later without losing progress—something free-form prompts can't do.
|
||||
|
||||
**Quality**: Sequential enforcement prevents shortcuts. The AI must complete each step fully before moving on, ensuring thorough, complete outputs instead of rushed, half-baked results.
|
||||
|
||||
---
|
||||
|
||||
## How Workflows Work
|
||||
|
||||
### The Basic Structure
|
||||
|
||||
Workflows consist of multiple markdown files, each representing one step:
|
||||
|
||||
```
|
||||
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
|
||||
│ Step 1 │ → │ Step 2 │ → │ Step 3 │ → │ Complete │
|
||||
│ Discover │ │ Define │ │ Build │ │ Output │
|
||||
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
|
||||
my-workflow/
|
||||
├── workflow.md # Entry point and configuration
|
||||
├── steps/ # Step files (steps-c/ for create, steps-e/ for edit, steps-v/ for validate)
|
||||
│ ├── step-01-init.md
|
||||
│ ├── step-02-profile.md
|
||||
│ └── step-N-final.md
|
||||
├── data/ # Reference materials, CSVs, examples
|
||||
└── templates/ # Output document templates
|
||||
```
|
||||
|
||||
**Key characteristics:**
|
||||
- **Progressive** - Each step builds on the previous
|
||||
- **Interactive** - Workflows can pause for user input
|
||||
- **Reusable** - The same workflow produces consistent results
|
||||
- **Composable** - Workflow steps can call other workflow steps, or whole other workflows!
|
||||
- **LLM Reinforcement** - Some rules or info is repeated in each step file ensuring certain rules are always top of agent mind, even during context heavy processes or very long workflows!
|
||||
The `workflow.md` file is minimal—it contains the workflow name, description, goal, the AI's role, and how to start. Importantly, it does not list all steps or detail what each does. This is progressive disclosure in action.
|
||||
|
||||
## Workflow Types
|
||||
### Sequential Execution
|
||||
|
||||
### Planning Workflows
|
||||
Workflows execute in strict sequence: `step-01 → step-02 → step-03 → ... → step-N`
|
||||
|
||||
Generate project artifacts like requirements, architecture, and task breakdowns.
|
||||
The AI cannot skip steps or optimize the sequence. It must complete each step fully before loading the next. This ensures thoroughness and prevents shortcuts that compromise quality.
|
||||
|
||||
**Examples:** Brief creation, PRD authoring, architecture design, sprint planning
|
||||
### Continuable Workflows
|
||||
|
||||
### Execution Workflows
|
||||
Some workflows are complex enough that users might need multiple sessions. These "continuable workflows" track which steps are complete in the output document's frontmatter, so users can stop and resume later without losing progress.
|
||||
|
||||
Guide implementation of specific tasks or features.
|
||||
Use continuable workflows when:
|
||||
- The workflow produces large documents
|
||||
- Multiple sessions are likely
|
||||
- Complex decisions benefit from reflection
|
||||
- The workflow has many steps (8+)
|
||||
|
||||
**Examples:** Code implementation, code review, testing, deployment
|
||||
Keep it simple (single-session) when tasks are quick, focused, and can be completed in one sitting.
|
||||
|
||||
### Support Workflows
|
||||
### Workflow Chaining
|
||||
|
||||
Handle cross-cutting concerns and creative processes.
|
||||
Workflows can be chained together where outputs become inputs. The BMM module pipeline is a perfect example:
|
||||
|
||||
**Examples:** Brainstorming, retrospectives, root cause analysis
|
||||
|
||||
## Progressive Disclosure
|
||||
|
||||
BMAD workflows use **progressive disclosure** - each step only knows about its immediate next step and what it is currently meant to do. This:
|
||||
|
||||
- Reduces cognitive load on the AI
|
||||
- Ensures each step gets full attention
|
||||
- Allows for conditional routing based on previous outcomes
|
||||
- Makes workflows easier to debug and modify
|
||||
|
||||
## Menu-Driven Interaction
|
||||
|
||||
Most workflows use interactive menus with standard options:
|
||||
|
||||
| Option | Purpose |
|
||||
| ---------------- | -------------------------------------------------- |
|
||||
| **[A] Advanced** | Invoke deeper reasoning techniques |
|
||||
| **[P] Party** | Get multiple agent perspectives |
|
||||
| **[C] Continue** | Proceed to next step after all writes are complete |
|
||||
|
||||
## Workflow Files
|
||||
|
||||
Workflows are markdown files with structured frontmatter - this front matter also allows them to easily work as skills and also slash command loaded:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: 'my-workflow'
|
||||
description: 'What this workflow does and when it should be used or loaded automatically (or call out if it should be requested to run explicitly by the user)'
|
||||
---
|
||||
```
|
||||
brainstorming → research → brief → PRD → UX → architecture → epics → sprint-planning
|
||||
↓
|
||||
implement-story → review → repeat
|
||||
```
|
||||
|
||||
The content in the workflow file is very minimal, sets up the reinforcement of the agent persona and reminder that it is a facilitator working with a user, lays out rules of processing steps only when told to do a specific step, loads all config file variables needed by the workflow, and then routes to step 1. No other info about other steps should be in this workflow file. Keeping it as small and lean as possible help in compilation as a skill, as overall size of the skill main file (workflow.md) is critical to keep small.
|
||||
Each workflow checks for required inputs from prior workflows, validates they're complete, and produces output for the next workflow. This creates powerful end-to-end pipelines for complex processes.
|
||||
|
||||
## Creating Custom Workflows
|
||||
### The Tri-Modal Pattern
|
||||
|
||||
The **BMAD Builder (BMB)** module includes workflows for creating custom workflows. See [BMB Documentation](../modules/bmb-bmad-builder/) for details.
|
||||
For critical workflows that produce important artifacts, BMAD uses a tri-modal structure: Create, Validate, and Edit. Each mode is a separate workflow path that can run independently or flow into the others.
|
||||
|
||||
**Create mode** builds new artifacts from scratch. But here's where it gets interesting: create mode can also function as a conversion tool. Feed it a non-compliant document—something that doesn't follow BMAD standards—and it will extract the essential content and rebuild it as a compliant artifact. This means you can bring in existing work and automatically upgrade it to follow proper patterns.
|
||||
|
||||
**Validate mode** runs standalone and checks artifacts against standards. Because it's separate, you can run validation whenever you want—immediately after creation, weeks later when things have changed, or even using a different LLM entirely. It's like having a quality assurance checkpoint that's always available but never forced.
|
||||
|
||||
**Edit mode** modifies existing artifacts while enforcing standards. As you update documents to reflect changing requirements or new understanding, edit mode ensures you don't accidentally drift away from the patterns that make the artifacts useful. It checks compliance as you work and can route back to create mode if it detects something that needs full conversion.
|
||||
|
||||
All BMAD planning workflows and the BMB module (will) use this tri-modal pattern. The pristine example is the workflow workflow in BMB—it creates workflow specifications, validates them against standards, and lets you edit them while maintaining compliance. You can study that workflow to see the pattern in action.
|
||||
|
||||
This tri-modal approach gives you the best of both worlds: the creativity and flexibility to build what you need, the quality assurance of validation that can run anytime, and the ability to iterate while staying true to standards that make the artifacts valuable across sessions and team members.
|
||||
|
||||
---
|
||||
|
||||
**Next:** Learn about [Modules](./modules.md) to see how agents and workflows are organized.
|
||||
## Design Decisions
|
||||
|
||||
Before building a workflow, answer these questions:
|
||||
|
||||
**Module affiliation**: Is this standalone or part of a module? Module-based workflows can access module-specific variables and reference other workflow outputs. Also when part of a module, generally they will be associated to an agent.
|
||||
|
||||
**Continuable or single-session?**: Will users need multiple sessions, or can this be completed in one sitting?
|
||||
|
||||
**Edit/Validate support?**: Do you need Create/Edit/Validate modes (tri-modal structure)? Use tri-modal for complex, critical workflows requiring quality assurance. Use create-only for simple, one-off workflows.
|
||||
|
||||
**Document output?**: Does this produce a persistent file, or perform actions without output?
|
||||
|
||||
**Intent or prescriptive?**: Is this intent-based facilitation (most workflows) or prescriptive compliance (medical, legal, regulated)?
|
||||
|
||||
---
|
||||
|
||||
## Learning from Examples
|
||||
|
||||
The best way to understand workflows is to study real examples. Look at the official BMAD modules:
|
||||
|
||||
- **BMB (Module Builder)**: Workflow and agent creation workflows
|
||||
- **BMM (Business Method Module)**: Complete software development pipeline from brainstorming through sprint planning
|
||||
- **BMGD (Game Development Module)**: Game design briefs, narratives, architecture
|
||||
- **CIS (Creativity, Innovation, Strategy)**: Brainstorming, design thinking, storytelling, innovation strategy
|
||||
|
||||
Study the workflow.md files to understand how each workflow starts. Examine step files to see how instructions are structured. Notice the frontmatter variables, menu handling, and how steps chain together.
|
||||
|
||||
Copy patterns that work. Adapt them to your domain. The structure is consistent across all workflows—the content and steps change, but the architecture stays the same.
|
||||
|
||||
---
|
||||
|
||||
## When to Use Workflows
|
||||
|
||||
Use workflows when:
|
||||
|
||||
- **Tasks are multi-step and complex**: Break down complexity into manageable pieces
|
||||
- **Quality and completeness matter**: Sequential enforcement ensures nothing gets missed
|
||||
- **Repeatability is important**: Get consistent results every time
|
||||
- **Tasks span multiple sessions**: Continuable workflows preserve progress
|
||||
- **You need to chain processes**: Output of one workflow becomes input of another
|
||||
- **Compliance or standards matter**: Enforce required steps and documentation
|
||||
|
||||
Don't use workflows when:
|
||||
|
||||
- **Tasks are simple and one-off**: A single prompt works fine for quick questions
|
||||
- **Flexibility trumps structure**: Free-form conversation is better for exploration
|
||||
|
||||
Modified BMad Workflows
|
||||
|
||||
- **Tasks are truly one-step**
|
||||
|
||||
If there's only one thing to do and it can be explained in under about 300 lines - don't bother with step files. Instead, you can still have
|
||||
a short single file workflow.md file.
|
||||
|
||||
---
|
||||
|
||||
## The Bottom Line
|
||||
|
||||
Workflows transform AI from a tool that gives variable, unpredictable results into a reliable system for complex, multi-step processes. Through progressive disclosure, sequential execution, guided facilitation, and thoughtful design, workflows give you control and repeatability that ad-hoc prompting alone can't match.
|
||||
|
||||
They're not just for software development. You can create workflows for any guided process - meal planning, course design, therapy intake, tax preparation, document processing, creative writing, event planning—any complex task that benefits from structure and thoroughness.
|
||||
|
||||
Start simple. Study examples. Build workflows for your own domain. You'll wonder how you ever got by with just prompts.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ The BMAD Builder (BMB) module provides an interactive workflow that guides you t
|
|||
**Prerequisites:**
|
||||
- BMAD installed with the BMB module
|
||||
- An idea for what you want your agent to do
|
||||
- About 15-30 minutes for your first agent
|
||||
|
||||
**Know Before You Go:**
|
||||
- What problem should your agent solve?
|
||||
|
|
@ -22,20 +21,14 @@ The BMAD Builder (BMB) module provides an interactive workflow that guides you t
|
|||
|
||||
### 1. Start the Workflow
|
||||
|
||||
In your IDE (Claude Code, Cursor, etc.), invoke the create-agent workflow:
|
||||
|
||||
```
|
||||
"Run the BMAD Builder create-agent workflow"
|
||||
```
|
||||
|
||||
Or trigger it via the BMAD Master menu.
|
||||
In your IDE (Claude Code, Cursor, etc.), invoke the create-agent workflow with the agent-builder agent.
|
||||
|
||||
### 2. Follow the Steps
|
||||
|
||||
The workflow guides you through:
|
||||
|
||||
| Step | What You'll Do |
|
||||
|------|----------------|
|
||||
| ------------------------- | -------------------------------------------- |
|
||||
| **Brainstorm** (optional) | Explore ideas with creative techniques |
|
||||
| **Discovery** | Define the agent's purpose and goals |
|
||||
| **Type & Metadata** | Choose Simple or Expert, name your agent |
|
||||
|
|
@ -97,7 +90,7 @@ The workflow will help you decide, but here's the quick reference:
|
|||
Your agent's personality is defined by four fields:
|
||||
|
||||
| Field | Purpose | Example |
|
||||
|-------|---------|---------|
|
||||
| ----------------------- | -------------- | ----------------------------------------------------------------- |
|
||||
| **Role** | What they do | "Senior code reviewer who catches bugs and suggests improvements" |
|
||||
| **Identity** | Who they are | "Friendly but exacting, believes clean code is a craft" |
|
||||
| **Communication Style** | How they speak | "Direct, constructive, explains the 'why' behind suggestions" |
|
||||
|
|
|
|||
|
|
@ -280,6 +280,7 @@
|
|||
"integrity": "sha512-NL76o/BoEgU4ObY5oBEC3o6KSPpuXsnSta00tAxTm1iKUWOGR34DQEKhUt8xMHhMKleUNPM/rLPFiIVtfsGU8w==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@algolia/client-common": "5.46.1",
|
||||
"@algolia/requester-browser-xhr": "5.46.1",
|
||||
|
|
@ -429,6 +430,7 @@
|
|||
"integrity": "sha512-yDBHV9kQNcr2/sUr9jghVyz9C3Y5G2zUM2H2lo+9mKv4sFgbA8s8Z9t8D1jiTkGoO/NoIfKMyKWr4s6CN23ZwQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@ampproject/remapping": "^2.2.0",
|
||||
"@babel/code-frame": "^7.27.1",
|
||||
|
|
@ -2527,6 +2529,7 @@
|
|||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"engines": {
|
||||
"node": ">=18"
|
||||
},
|
||||
|
|
@ -2550,6 +2553,7 @@
|
|||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"engines": {
|
||||
"node": ">=18"
|
||||
}
|
||||
|
|
@ -2664,6 +2668,7 @@
|
|||
"integrity": "sha512-orRsuYpJVw8LdAwqqLykBj9ecS5/cRHlI5+nvTo8LcCKmzDmqVORXtOIYEEQuL9D4BxtA1lm5isAqzQZCoQ6Eg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"cssesc": "^3.0.0",
|
||||
"util-deprecate": "^1.0.2"
|
||||
|
|
@ -3101,6 +3106,7 @@
|
|||
"integrity": "sha512-orRsuYpJVw8LdAwqqLykBj9ecS5/cRHlI5+nvTo8LcCKmzDmqVORXtOIYEEQuL9D4BxtA1lm5isAqzQZCoQ6Eg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"cssesc": "^3.0.0",
|
||||
"util-deprecate": "^1.0.2"
|
||||
|
|
@ -4245,6 +4251,7 @@
|
|||
"integrity": "sha512-C5wZsGuKTY8jEYsqdxhhFOe1ZDjH0uIYJ9T/jebHwkyxqnr4wW0jTkB72OMqNjsoQRcb0JN3PcSeTwFlVgzCZg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@docusaurus/core": "3.9.2",
|
||||
"@docusaurus/logger": "3.9.2",
|
||||
|
|
@ -5924,6 +5931,7 @@
|
|||
"integrity": "sha512-f++rKLQgUVYDAtECQ6fn/is15GkEH9+nZPM3MS0RcxVqoTfawHvDlSCH7JbMhAM6uJ32v3eXLvLmLvjGu7PTQw==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@types/mdx": "^2.0.0"
|
||||
},
|
||||
|
|
@ -6414,6 +6422,7 @@
|
|||
"integrity": "sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@babel/core": "^7.21.3",
|
||||
"@svgr/babel-preset": "8.1.0",
|
||||
|
|
@ -6855,6 +6864,7 @@
|
|||
"integrity": "sha512-aPTXCrfwnDLj4VvXrm+UUCQjNEvJgNA8s5F1cvwQU+3KNltTOkBm1j30uNLyqqPNe7gE3KFzImYoZEfLhp4Yow==",
|
||||
"devOptional": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"undici-types": "~7.10.0"
|
||||
}
|
||||
|
|
@ -6896,6 +6906,7 @@
|
|||
"integrity": "sha512-MWtvHrGZLFttgeEj28VXHxpmwYbor/ATPYbBfSFZEIRK0ecCFLl2Qo55z52Hss+UV9CRN7trSeq1zbgx7YDWWg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"csstype": "^3.2.2"
|
||||
}
|
||||
|
|
@ -7572,6 +7583,7 @@
|
|||
"integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"bin": {
|
||||
"acorn": "bin/acorn"
|
||||
},
|
||||
|
|
@ -7674,6 +7686,7 @@
|
|||
"integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"fast-deep-equal": "^3.1.1",
|
||||
"fast-json-stable-stringify": "^2.0.0",
|
||||
|
|
@ -7743,6 +7756,7 @@
|
|||
"integrity": "sha512-39ol8Ulqb3MntofkXHlrcXKyU8BU0PXvQrXPBIX6eXj/EO4VT7651mhGVORI2oF8ydya9nFzT3fYDoqme/KL6w==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@algolia/abtesting": "1.12.1",
|
||||
"@algolia/client-abtesting": "5.46.1",
|
||||
|
|
@ -8597,6 +8611,7 @@
|
|||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"baseline-browser-mapping": "^2.9.0",
|
||||
"caniuse-lite": "^1.0.30001759",
|
||||
|
|
@ -10135,6 +10150,7 @@
|
|||
"integrity": "sha512-orRsuYpJVw8LdAwqqLykBj9ecS5/cRHlI5+nvTo8LcCKmzDmqVORXtOIYEEQuL9D4BxtA1lm5isAqzQZCoQ6Eg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"cssesc": "^3.0.0",
|
||||
"util-deprecate": "^1.0.2"
|
||||
|
|
@ -11289,6 +11305,7 @@
|
|||
"integrity": "sha512-RNCHRX5EwdrESy3Jc9o8ie8Bog+PeYvvSR8sDGoZxNFTvZ4dlxUB3WzQ3bQMztFrSRODGrLLj8g6OFuGY/aiQg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@eslint-community/eslint-utils": "^4.2.0",
|
||||
"@eslint-community/regexpp": "^4.12.1",
|
||||
|
|
@ -18596,6 +18613,7 @@
|
|||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"nanoid": "^3.3.11",
|
||||
"picocolors": "^1.1.1",
|
||||
|
|
@ -19547,6 +19565,7 @@
|
|||
"integrity": "sha512-orRsuYpJVw8LdAwqqLykBj9ecS5/cRHlI5+nvTo8LcCKmzDmqVORXtOIYEEQuL9D4BxtA1lm5isAqzQZCoQ6Eg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"cssesc": "^3.0.0",
|
||||
"util-deprecate": "^1.0.2"
|
||||
|
|
@ -20131,6 +20150,7 @@
|
|||
"integrity": "sha512-I7AIg5boAr5R0FFtJ6rCfD+LFsWHp81dolrFD8S79U9tb8Az2nGrJncnMSnys+bpQJfRUzqs9hnA81OAA3hCuQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"bin": {
|
||||
"prettier": "bin/prettier.cjs"
|
||||
},
|
||||
|
|
@ -20379,9 +20399,9 @@
|
|||
"license": "MIT"
|
||||
},
|
||||
"node_modules/qs": {
|
||||
"version": "6.14.0",
|
||||
"resolved": "https://registry.npmjs.org/qs/-/qs-6.14.0.tgz",
|
||||
"integrity": "sha512-YWWTjgABSKcvs/nWBi9PycY/JiPJqOD4JA6o9Sej2AtvSGarXxKC3OQSk4pAarbdQlKAh5D4FCQkJNkW+GAn3w==",
|
||||
"version": "6.14.1",
|
||||
"resolved": "https://registry.npmjs.org/qs/-/qs-6.14.1.tgz",
|
||||
"integrity": "sha512-4EK3+xJl8Ts67nLYNwqw/dsFVnCf+qR7RgXSK9jEEm9unao3njwMDdmsdvoKBKHzxd7tCYz5e5M+SnMjdtXGQQ==",
|
||||
"dev": true,
|
||||
"license": "BSD-3-Clause",
|
||||
"dependencies": {
|
||||
|
|
@ -20526,6 +20546,7 @@
|
|||
"integrity": "sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"loose-envify": "^1.1.0"
|
||||
},
|
||||
|
|
@ -20539,6 +20560,7 @@
|
|||
"integrity": "sha512-5m4nQKp+rZRb09LNH59GM4BxTh9251/ylbKIbpe7TpGxfJ+9kv6BLkLBXIjjspbgbnIBNqlI23tRnTWT0snUIw==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"loose-envify": "^1.1.0",
|
||||
"scheduler": "^0.23.2"
|
||||
|
|
@ -20600,6 +20622,7 @@
|
|||
"integrity": "sha512-YMMxTUQV/QFSnbgrP3tjDzLHRg7vsbMn8e9HAa8o/1iXoiomo48b7sk/kkmWEuWNDPJVlKSJRB6Y2fHqdJk+SQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@types/react": "*"
|
||||
},
|
||||
|
|
@ -20630,6 +20653,7 @@
|
|||
"integrity": "sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@babel/runtime": "^7.12.13",
|
||||
"history": "^4.9.0",
|
||||
|
|
@ -21578,6 +21602,7 @@
|
|||
"integrity": "sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"fast-deep-equal": "^3.1.3",
|
||||
"fast-uri": "^3.0.1",
|
||||
|
|
@ -22991,6 +23016,7 @@
|
|||
"integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"engines": {
|
||||
"node": ">=12"
|
||||
},
|
||||
|
|
@ -23126,7 +23152,8 @@
|
|||
"version": "2.8.1",
|
||||
"resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz",
|
||||
"integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==",
|
||||
"license": "0BSD"
|
||||
"license": "0BSD",
|
||||
"peer": true
|
||||
},
|
||||
"node_modules/type-check": {
|
||||
"version": "0.4.0",
|
||||
|
|
@ -24014,6 +24041,7 @@
|
|||
"integrity": "sha512-Qphch25abbMNtekmEGJmeRUhLDbe+QfiWTiqpKYkpCOWY64v9eyl+KRRLmqOFA2AvKPpc9DC6+u2n76tQLBoaA==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@types/eslint-scope": "^3.7.7",
|
||||
"@types/estree": "^1.0.8",
|
||||
|
|
@ -24811,6 +24839,7 @@
|
|||
"integrity": "sha512-JInaHOamG8pt5+Ey8kGmdcAcg3OL9reK8ltczgHTAwNhMys/6ThXHityHxVV2p3fkw/c+MAvBHFVYHFZDmjMCQ==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"funding": {
|
||||
"url": "https://github.com/sponsors/colinhacks"
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,19 +1,36 @@
|
|||
# Step 3: Interactive Technique Execution and Facilitation
|
||||
|
||||
---
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
---
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
|
||||
- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
|
||||
- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
|
||||
- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What domain haven't we explored yet? What would make this idea surprising or 'uncomfortable' for the user?"
|
||||
- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact).
|
||||
- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" concepts.
|
||||
- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
|
||||
- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
|
||||
- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
|
||||
- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
|
||||
- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
|
||||
|
||||
## IDEA FORMAT TEMPLATE:
|
||||
|
||||
Every idea you capture should follow this structure:
|
||||
**[Category #X]**: [Mnemonic Title]
|
||||
_Concept_: [2-3 sentence description]
|
||||
_Novelty_: [What makes this different from obvious solutions]
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Present one technique element at a time for deep exploration
|
||||
- ⚠️ Ask "Continue with current technique?" before moving to next technique
|
||||
- 💾 Document insights and ideas as they emerge organically
|
||||
- 💾 Document insights and ideas using the **IDEA FORMAT TEMPLATE**
|
||||
- 📖 Follow user's creative energy and interests within technique structure
|
||||
- 🚫 FORBIDDEN rushing through technique elements without user engagement
|
||||
|
||||
|
|
@ -142,6 +159,26 @@ Before moving to next technique element:
|
|||
|
||||
**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
|
||||
|
||||
### 4.1. Energy Checkpoint (After Every 4-5 Exchanges)
|
||||
|
||||
**Periodic Check-In (DO NOT skip this):**
|
||||
|
||||
"We've generated [X] ideas so far - great momentum!
|
||||
|
||||
**Quick energy check:**
|
||||
|
||||
- Want to **keep pushing** on this angle?
|
||||
- **Switch techniques** for a fresh perspective?
|
||||
- Or are you feeling like we've **thoroughly explored** this space?
|
||||
|
||||
Remember: The goal is quantity first - we can organize later. What feels right?"
|
||||
|
||||
**IMPORTANT:** Default to continuing exploration. Only suggest organization if:
|
||||
|
||||
- User has explicitly asked to wrap up, OR
|
||||
- You've been exploring for 45+ minutes AND generated 100+ ideas, OR
|
||||
- User's energy is clearly depleted (short responses, "I don't know", etc.)
|
||||
|
||||
### 4a. Handle Immediate Technique Transition
|
||||
|
||||
**When user says "next technique" or "move on":**
|
||||
|
|
@ -208,13 +245,15 @@ This connects beautifully with what we discovered earlier about _[previous conne
|
|||
|
||||
**After Deep Exploration:**
|
||||
|
||||
"Let me summarize what we've uncovered in this exploration:
|
||||
"Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**:
|
||||
|
||||
**Key Ideas Generated:**
|
||||
|
||||
- **[Idea 1]:** [Context and development]
|
||||
- **[Idea 2]:** [How this emerged and evolved]
|
||||
- **[Idea 3]:** [User's insight plus your coaching contribution]
|
||||
**[Category #X]**: [Mnemonic Title]
|
||||
_Concept_: [2-3 sentence description]
|
||||
_Novelty_: [What makes this different from obvious solutions]
|
||||
|
||||
(Repeat for all ideas generated)
|
||||
|
||||
**Creative Breakthrough:** [Most innovative insight from the dialogue]
|
||||
|
||||
|
|
@ -243,17 +282,29 @@ After final technique element:
|
|||
|
||||
**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
|
||||
|
||||
**Ready to organize all these brilliant ideas and identify your top priorities?**
|
||||
[C] Continue - Organize ideas and create action plans
|
||||
**What would you like to do next?**
|
||||
|
||||
### 8. Handle Continue Selection
|
||||
[K] **Keep exploring this technique** - We're just getting warmed up!
|
||||
[T] **Try a different technique** - Fresh perspective on the same topic
|
||||
[A] **Go deeper on a specific idea** - Develop a promising concept further (Advanced Elicitation)
|
||||
[B] **Take a quick break** - Pause and return with fresh energy
|
||||
[C] **Move to organization** - Only when you feel we've thoroughly explored
|
||||
|
||||
#### If 'C' (Continue):
|
||||
**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
|
||||
|
||||
### 8. Handle Menu Selection
|
||||
|
||||
#### If 'C' (Move to organization):
|
||||
|
||||
- **Append the technique execution content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
|
||||
- **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
|
||||
- **Load:** `./step-04-idea-organization.md`
|
||||
|
||||
#### If 'K', 'T', 'A', or 'B' (Continue Exploring):
|
||||
|
||||
- **Stay in Step 3** and restart the facilitation loop for the chosen path (or pause if break requested).
|
||||
- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}`
|
||||
|
||||
### 9. Update Documentation
|
||||
|
||||
Update frontmatter and document with interactive session insights:
|
||||
|
|
@ -279,6 +330,7 @@ facilitation_notes: [key insights about user's creative process]
|
|||
|
||||
- **Interactive Focus:** [Main exploration directions]
|
||||
- **Key Breakthroughs:** [Major insights from coaching dialogue]
|
||||
|
||||
- **User Creative Strengths:** [What user demonstrated]
|
||||
- **Energy Level:** [Observation about engagement]
|
||||
|
||||
|
|
@ -308,6 +360,9 @@ When user selects 'C', append the content directly to `{output_folder}/analysis/
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Minimum 100 ideas generated before organization is offered
|
||||
✅ User explicitly confirms readiness to conclude (not AI-initiated)
|
||||
✅ Multiple technique exploration encouraged over single-technique completion
|
||||
✅ True back-and-forth facilitation rather than question-answer format
|
||||
✅ User's creative energy and interests guide technique direction
|
||||
✅ Deep exploration of promising ideas before moving on
|
||||
|
|
@ -318,6 +373,10 @@ When user selects 'C', append the content directly to `{output_folder}/analysis/
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Offering organization after only one technique or <20 ideas
|
||||
❌ AI initiating conclusion without user explicitly requesting it
|
||||
❌ Treating technique completion as session completion signal
|
||||
❌ Rushing to document rather than staying in generative mode
|
||||
❌ Rushing through technique elements without user engagement
|
||||
❌ Not following user's creative energy and interests
|
||||
❌ Missing opportunities to develop promising ideas deeper
|
||||
|
|
|
|||
|
|
@ -10,6 +10,12 @@ context_file: '' # Optional context file path for project-specific guidance
|
|||
|
||||
**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`.
|
||||
|
||||
**Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
|
||||
|
||||
**Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence.
|
||||
|
||||
**Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
|
||||
|
||||
---
|
||||
|
||||
## WORKFLOW ARCHITECTURE
|
||||
|
|
@ -41,6 +47,7 @@ Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
|
|||
- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
|
||||
- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
|
||||
- `context_file` = Optional context file path from workflow invocation for project-specific guidance
|
||||
- `advancedElicitationTask` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ For module agents referencing external workflow files.
|
|||
description: '[CP] Create Product Requirements Document'
|
||||
|
||||
- trigger: GB or fuzzy match on brainstorm
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
|
||||
description: '[GB] Guided brainstorming session'
|
||||
|
||||
# Planned but unimplemented
|
||||
|
|
@ -112,11 +112,11 @@ menu:
|
|||
|
||||
```yaml
|
||||
# ✅ CORRECT
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
|
||||
data: '{project-root}/_data/metrics.csv'
|
||||
|
||||
# ❌ WRONG
|
||||
exec: '../../../core/workflows/brainstorming/workflow.yaml'
|
||||
exec: '../../../core/workflows/brainstorming/workflow.md'
|
||||
```
|
||||
|
||||
**Available variables:**
|
||||
|
|
@ -213,8 +213,8 @@ menu:
|
|||
description: '[WI] Initialize workflow path'
|
||||
|
||||
- trigger: BS or fuzzy match on brainstorm
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
|
||||
description: '[BS] Guided brainstorming'
|
||||
exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
|
||||
description: '[BS] Guided brainstorming [K,T,A,B,C]'
|
||||
|
||||
- trigger: CP or fuzzy match on create-prd
|
||||
exec: '{project-root}/_bmad/bmm/workflows/create-prd/workflow.md'
|
||||
|
|
|
|||
|
|
@ -93,10 +93,11 @@ Handle each scenario appropriately with user prompts.
|
|||
**Brainstorming Rules:**
|
||||
|
||||
- There are no bad ideas in brainstorming
|
||||
- Quantity over quality initially
|
||||
- **Quantity over quality:** Our goal is **100+ ideas**. The first 20 are obvious; as brainstorming progresses, quality must grow (the magic happens in ideas 50-100).
|
||||
- Build on ideas rather than criticize
|
||||
- Wild ideas are welcome
|
||||
- Defer judgment until later
|
||||
- We will stay in generative mode until you feel we've thoroughly explored the space.
|
||||
|
||||
**What we'll do:**
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ outputFile: '{output_folder}/brainstorming-session-{date}.md'
|
|||
# Context Files
|
||||
gameContext: '{workflow_path}/game-context.md'
|
||||
gameBrainMethods: '{workflow_path}/game-brain-methods.csv'
|
||||
coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
|
||||
coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
|
||||
---
|
||||
|
||||
# Step 2: Load Context
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
|
|||
outputFile: '{output_folder}/brainstorming-session-{date}.md'
|
||||
|
||||
# Core Brainstorming Reference
|
||||
coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
|
||||
coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
|
|
@ -31,6 +31,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
|
|||
|
||||
### Universal Rules:
|
||||
|
||||
- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
|
||||
- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
|
||||
- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
|
||||
- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What mechanic/theme haven't we explored yet? What would make this concept 'break the genre'?"
|
||||
- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., Mechanics -> Monetization -> Lore -> Accessibility).
|
||||
- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" game loops.
|
||||
- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
|
||||
- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
|
||||
- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
|
||||
- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
|
||||
- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
|
||||
- NEVER generate content without user input
|
||||
- CRITICAL: Read the complete step file before taking any action
|
||||
- CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
|
|
@ -38,6 +49,13 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
|
|||
- NEVER mention time estimates
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
## IDEA FORMAT TEMPLATE:
|
||||
|
||||
Every idea you capture should follow this structure:
|
||||
**[Category #X]**: [Mnemonic Title]
|
||||
_Core Loop_: [2-3 sentence description of player action]
|
||||
_Novelty_: [What makes this different from generic games]
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- You are a creative game design facilitator
|
||||
|
|
@ -55,15 +73,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
|
|||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- Show your analysis before taking any action
|
||||
- Present A/P/C menu after ideation session
|
||||
- Present the exploration menu after ideation session
|
||||
- ONLY proceed when user chooses C (Continue)
|
||||
- Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
|
||||
## COLLABORATION MENUS (A/P/C):
|
||||
## EXPLORATION & COLLABORATION MENU:
|
||||
|
||||
- **A (Advanced Elicitation)**: Dig deeper into promising ideas
|
||||
- **P (Party Mode)**: Get multiple perspectives on concepts
|
||||
- **C (Continue)**: Save ideas and complete session
|
||||
- [K] **Keep exploring current technique** - Push for more ideas using the current method
|
||||
- [T] **Try a different game design technique** - Switch to another method from the library
|
||||
- [A] **Advanced Elicitation** - Dig deeper into promising ideas using reasoning techniques
|
||||
- [P] **Party Mode** - Get multiple perspectives on concepts from other agents
|
||||
- [C] **Continue** - Save ideas and move to organization phase
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
|
|
@ -177,30 +197,16 @@ Your choice:"
|
|||
|
||||
### 7. Generate Ideation Section
|
||||
|
||||
Based on all ideas captured, prepare the content:
|
||||
Based on all ideas captured, prepare the content using our **IDEA FORMAT TEMPLATE**:
|
||||
|
||||
```markdown
|
||||
## Ideas Generated
|
||||
|
||||
### Concept 1: {{concept_name}}
|
||||
**[Category #X]**: [Mnemonic Title]
|
||||
_Core Loop_: [2-3 sentence description of player action]
|
||||
_Novelty_: [What makes this different from generic games]
|
||||
|
||||
{{full_concept_description}}
|
||||
|
||||
**Core Elements:**
|
||||
|
||||
- {{element_1}}
|
||||
- {{element_2}}
|
||||
|
||||
**Questions to Explore:**
|
||||
|
||||
- {{question_1}}
|
||||
- {{question_2}}
|
||||
|
||||
---
|
||||
|
||||
### Concept 2: {{concept_name}}
|
||||
|
||||
{{repeat_structure}}
|
||||
(Repeat for all ideas generated)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -211,10 +217,6 @@ Based on all ideas captured, prepare the content:
|
|||
## Promising Combinations
|
||||
|
||||
{{combination_ideas}}
|
||||
|
||||
## Raw Ideas List
|
||||
|
||||
{{all_ideas_bullet_points}}
|
||||
```
|
||||
|
||||
### 8. Present Content and Menu
|
||||
|
|
@ -229,30 +231,33 @@ Here's everything we captured:
|
|||
|
||||
**Session Stats:**
|
||||
|
||||
- Ideas generated: {{count}}
|
||||
- Concepts developed: {{count}}
|
||||
- Themes identified: {{count}}
|
||||
- Ideas generated: {{idea_count}}
|
||||
- Concepts developed: {{concept_count}}
|
||||
- Themes identified: {{theme_count}}
|
||||
|
||||
**Select an Option:**
|
||||
[A] Advanced Elicitation - Dig deeper into promising ideas
|
||||
[P] Party Mode - Get multiple perspectives on concepts
|
||||
[C] Continue - Save ideas and complete session (Step 4 of 4)"
|
||||
[K] **Keep exploring current technique** - We're just getting warmed up!
|
||||
[T] **Try a different game design technique** - Fresh perspective on the same concept
|
||||
[A] **Advanced Elicitation** - Go deeper on a specific concept (Dig deeper)
|
||||
[P] **Party Mode** - Get multiple perspectives on concepts from other agents
|
||||
[C] **Continue to Organization** - Only when you feel we've thoroughly explored (Step 4 of 4)
|
||||
|
||||
**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
|
||||
|
||||
### 9. Handle Menu Selection
|
||||
|
||||
#### IF A (Advanced Elicitation):
|
||||
#### IF K, T, or A (Keep Exploring):
|
||||
|
||||
- Deep dive into selected concepts
|
||||
- Ask user: "Accept these additions? (y/n)"
|
||||
- If yes: Update content, return to A/P/C menu
|
||||
- If no: Keep original, return to A/P/C menu
|
||||
- **Restart the ideation loop** based on the chosen path
|
||||
- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}`
|
||||
- Keep user in generative mode
|
||||
|
||||
#### IF P (Party Mode):
|
||||
|
||||
- Get diverse perspectives on concepts
|
||||
- Get diverse perspectives on concepts using `{partyModeWorkflow}`
|
||||
- Ask user: "Accept these perspectives? (y/n)"
|
||||
- If yes: Update content, return to A/P/C menu
|
||||
- If no: Keep original, return to A/P/C menu
|
||||
- If yes: Update content, return to exploration menu
|
||||
- If no: Keep original, return to exploration menu
|
||||
|
||||
#### IF C (Continue):
|
||||
|
||||
|
|
|
|||
|
|
@ -34,6 +34,8 @@ To begin, load and execute step-01-init.md:
|
|||
## Critical Rules
|
||||
|
||||
- This is a meta-workflow that orchestrates CIS brainstorming
|
||||
- **Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
|
||||
- **Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
|
||||
- Use game-specific techniques from game-brain-methods.csv
|
||||
- Apply game-context.md guidance throughout
|
||||
- **NEVER** mention time estimates
|
||||
|
|
@ -43,6 +45,7 @@ To begin, load and execute step-01-init.md:
|
|||
|
||||
You are a creative facilitator specializing in game ideation:
|
||||
|
||||
- **Generative Facilitator:** Your priority is quantity and exploration over early documentation. Keep the user in "Yes And" mode.
|
||||
- Draw out user's game concepts and ideas
|
||||
- Apply game-specific brainstorming techniques
|
||||
- Help users explore mechanics, themes, and experiences
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md"
|
|||
game_brain_methods: "{installed_path}/game-brain-methods.csv"
|
||||
|
||||
# CORE brainstorming workflow reference (for technique merging)
|
||||
core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
|
||||
core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
|
||||
|
||||
# Output configuration
|
||||
default_output_file: "{output_folder}/brainstorming-session-{date}.md"
|
||||
|
|
@ -58,5 +58,5 @@ web_bundle:
|
|||
# Context files
|
||||
- "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
|
||||
- "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
|
||||
existing_workflows:
|
||||
- core_brainstorming: "_bmad/core/workflows/brainstorming/workflow.yaml"
|
||||
dependencies:
|
||||
- "_bmad/core/workflows/brainstorming/workflow.md"
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ agent:
|
|||
description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
|
||||
|
||||
- trigger: QD or fuzzy match on quick-dev
|
||||
workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
|
||||
workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
|
||||
description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
|
||||
|
||||
- trigger: CR or fuzzy match on code-review
|
||||
|
|
|
|||
|
|
@ -17,5 +17,5 @@ agent:
|
|||
|
||||
menu:
|
||||
- trigger: BS or fuzzy match on brainstorm
|
||||
workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
|
||||
workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
|
||||
description: "[BS] Guide me through Brainstorming any topic"
|
||||
|
|
|
|||
Loading…
Reference in New Issue