feat(bmad): initialize comprehensive BMAD system with agents and configurations

Add complete BMAD method implementation including:
- 20+ specialized agents (dev, qa, pm, architect, etc.)
- 50+ reusable tasks for workflow automation
- IDE-specific configurations for Claude, Cursor, Gemini
- Chat modes and rule definitions for various environments
- Web bundles and team configurations
- Documentation and checklists for BMAD processes

This establishes the full BMAD ecosystem for collaborative development workflows.

.claude/commands/bmad-cw/tasks/advanced-elicitation.md

@@ -0,0 +1,123 @@
+# /advanced-elicitation Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# Advanced Elicitation Task
+
+## Purpose
+
+- Provide optional reflective and brainstorming actions to enhance content quality
+- Enable deeper exploration of ideas through structured elicitation techniques
+- Support iterative refinement through multiple analytical perspectives
+- Usable during template-driven document creation or any chat conversation
+
+## Usage Scenarios
+
+### Scenario 1: Template Document Creation
+
+After outputting a section during document creation:
+
+1. **Section Review**: Ask user to review the drafted section
+2. **Offer Elicitation**: Present 9 carefully selected elicitation methods
+3. **Simple Selection**: User types a number (0-8) to engage method, or 9 to proceed
+4. **Execute & Loop**: Apply selected method, then re-offer choices until user proceeds
+
+### Scenario 2: General Chat Elicitation
+
+User can request advanced elicitation on any agent output:
+
+- User says "do advanced elicitation" or similar
+- Agent selects 9 relevant methods for the context
+- Same simple 0-9 selection process
+
+## Task Instructions
+
+### 1. Intelligent Method Selection
+
+**Context Analysis**: Before presenting options, analyze:
+
+- **Content Type**: Technical specs, user stories, architecture, requirements, etc.
+- **Complexity Level**: Simple, moderate, or complex content
+- **Stakeholder Needs**: Who will use this information
+- **Risk Level**: High-impact decisions vs routine items
+- **Creative Potential**: Opportunities for innovation or alternatives
+
+**Method Selection Strategy**:
+
+1. **Always Include Core Methods** (choose 3-4):
+   - Expand or Contract for Audience
+   - Critique and Refine
+   - Identify Potential Risks
+   - Assess Alignment with Goals
+
+2. **Context-Specific Methods** (choose 4-5):
+   - **Technical Content**: Tree of Thoughts, ReWOO, Meta-Prompting
+   - **User-Facing Content**: Agile Team Perspective, Stakeholder Roundtable
+   - **Creative Content**: Innovation Tournament, Escape Room Challenge
+   - **Strategic Content**: Red Team vs Blue Team, Hindsight Reflection
+
+3. **Always Include**: "Proceed / No Further Actions" as option 9
+
+### 2. Section Context and Review
+
+When invoked after outputting a section:
+
+1. **Provide Context Summary**: Give a brief 1-2 sentence summary of what the user should look for in the section just presented
+
+2. **Explain Visual Elements**: If the section contains diagrams, explain them briefly before offering elicitation options
+
+3. **Clarify Scope Options**: If the section contains multiple distinct items, inform the user they can apply elicitation actions to:
+   - The entire section as a whole
+   - Individual items within the section (specify which item when selecting an action)
+
+### 3. Present Elicitation Options
+
+**Review Request Process:**
+
+- Ask the user to review the drafted section
+- In the SAME message, inform them they can suggest direct changes OR select an elicitation method
+- Present 9 intelligently selected methods (0-8) plus "Proceed" (9)
+- Keep descriptions short - just the method name
+- Await simple numeric selection
+
+**Action List Presentation Format:**
+
+```text
+**Advanced Elicitation Options**
+Choose a number (0-8) or 9 to proceed:
+
+0. [Method Name]
+1. [Method Name]
+2. [Method Name]
+3. [Method Name]
+4. [Method Name]
+5. [Method Name]
+6. [Method Name]
+7. [Method Name]
+8. [Method Name]
+9. Proceed / No Further Actions
+```
+
+**Response Handling:**
+
+- **Numbers 0-8**: Execute the selected method, then re-offer the choice
+- **Number 9**: Proceed to next section or continue conversation
+- **Direct Feedback**: Apply user's suggested changes and continue
+
+### 4. Method Execution Framework
+
+**Execution Process:**
+
+1. **Retrieve Method**: Access the specific elicitation method from the elicitation-methods data file
+2. **Apply Context**: Execute the method from your current role's perspective
+3. **Provide Results**: Deliver insights, critiques, or alternatives relevant to the content
+4. **Re-offer Choice**: Present the same 9 options again until user selects 9 or gives direct feedback
+
+**Execution Guidelines:**
+
+- **Be Concise**: Focus on actionable insights, not lengthy explanations
+- **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
+- **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
+- **Maintain Flow**: Keep the process moving efficiently

.claude/commands/bmad-cw/tasks/analyze-reader-feedback.md

@@ -0,0 +1,27 @@
+# /analyze-reader-feedback Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 16. Analyze Reader Feedback
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: analyze-reader-feedback
+name: Analyze Reader Feedback
+description: Summarize reader comments, identify trends, update story bible.
+persona_default: beta-reader
+inputs:
+
+- publication-log.md
+  steps:
+- Cluster comments by theme.
+- Suggest course corrections.
+  output: retro.md
+  ...

.claude/commands/bmad-cw/tasks/analyze-story-structure.md

@@ -0,0 +1,71 @@
+# /analyze-story-structure Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# Analyze Story Structure
+
+## Purpose
+
+Perform comprehensive structural analysis of a narrative work to identify strengths, weaknesses, and improvement opportunities.
+
+## Process
+
+### 1. Identify Structure Type
+
+- Three-act structure
+- Five-act structure
+- Hero's Journey
+- Save the Cat beats
+- Freytag's Pyramid
+- Kishōtenketsu
+- In medias res
+- Non-linear/experimental
+
+### 2. Map Key Points
+
+- **Opening**: Hook, world establishment, character introduction
+- **Inciting Incident**: What disrupts the status quo?
+- **Plot Point 1**: What locks in the conflict?
+- **Midpoint**: What reversal/revelation occurs?
+- **Plot Point 2**: What raises stakes to maximum?
+- **Climax**: How does central conflict resolve?
+- **Resolution**: What new equilibrium emerges?
+
+### 3. Analyze Pacing
+
+- Scene length distribution
+- Tension escalation curve
+- Breather moment placement
+- Action/reflection balance
+- Chapter break effectiveness
+
+### 4. Evaluate Setup/Payoff
+
+- Track all setups (promises to reader)
+- Verify each has satisfying payoff
+- Identify orphaned setups
+- Find unsupported payoffs
+- Check Chekhov's guns
+
+### 5. Assess Subplot Integration
+
+- List all subplots
+- Track intersection with main plot
+- Evaluate resolution satisfaction
+- Check thematic reinforcement
+
+### 6. Generate Report
+
+Create structural report including:
+
+- Structure diagram
+- Pacing chart
+- Problem areas
+- Suggested fixes
+- Alternative structures
+
+## Output
+
+Comprehensive structural analysis with actionable recommendations

.claude/commands/bmad-cw/tasks/assemble-kdp-package.md

@@ -0,0 +1,33 @@
+# /assemble-kdp-package Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# tasks/assemble-kdp-package.md
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: assemble-kdp-package
+name: Assemble KDP Cover Package
+description: Compile final instructions, assets list, and compliance checklist for Amazon KDP upload.
+persona_default: cover-designer
+inputs:
+
+- cover-brief.md
+- cover-prompts.md
+  steps:
+- Calculate full‑wrap cover dimensions (front, spine, back) using trim size & page count.
+- List required bleed and margin values.
+- Provide layout diagram (ASCII or Mermaid) labeling zones.
+- Insert ISBN placeholder or user‑supplied barcode location.
+- Populate back‑cover content sections (blurb, reviews, author bio).
+- Export combined PDF instructions (design-package.md) with link placeholders for final JPEG/PNG.
+- Execute kdp-cover-ready-checklist; flag any unmet items.
+  output: design-package.md
+  ...

.claude/commands/bmad-cw/tasks/brainstorm-premise.md

@@ -0,0 +1,27 @@
+# /brainstorm-premise Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 1. Brainstorm Premise
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: brainstorm-premise
+name: Brainstorm Premise
+description: Rapidly generate and refine one‑sentence log‑line ideas for a new novel or story.
+persona_default: plot-architect
+steps:
+
+- Ask genre, tone, and any must‑have elements.
+- Produce 5–10 succinct log‑lines (max 35 words each).
+- Invite user to select or combine.
+- Refine the chosen premise into a single powerful sentence.
+  output: premise.txt
+  ...

.claude/commands/bmad-cw/tasks/build-world.md

@@ -0,0 +1,28 @@
+# /build-world Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 2. Build World
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: build-world
+name: Build World
+description: Create a concise world guide covering geography, cultures, magic/tech, and history.
+persona_default: world-builder
+inputs:
+
+- concept-brief.md
+  steps:
+- Summarize key themes from concept.
+- Draft World Guide using world-guide-tmpl.
+- Execute tasks#advanced-elicitation.
+  output: world-guide.md
+  ...

.claude/commands/bmad-cw/tasks/character-depth-pass.md

@@ -0,0 +1,26 @@
+# /character-depth-pass Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 9. Character Depth Pass
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: character-depth-pass
+name: Character Depth Pass
+description: Enrich character profiles with backstory and arc details.
+persona_default: character-psychologist
+inputs:
+
+- character-summaries.md
+  steps:
+- For each character, add formative events, internal conflicts, arc milestones.
+  output: characters.md
+  ...

.claude/commands/bmad-cw/tasks/create-doc.md

@@ -0,0 +1,107 @@
+# /create-doc Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# Create Document from Template (YAML Driven)
+
+## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
+
+**THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL**
+
+When this task is invoked:
+
+1. **DISABLE ALL EFFICIENCY OPTIMIZATIONS** - This workflow requires full user interaction
+2. **MANDATORY STEP-BY-STEP EXECUTION** - Each section must be processed sequentially with user feedback
+3. **ELICITATION IS REQUIRED** - When `elicit: true`, you MUST use the 1-9 format and wait for user response
+4. **NO SHORTCUTS ALLOWED** - Complete documents cannot be created without following this workflow
+
+**VIOLATION INDICATOR:** If you create a complete document without user interaction, you have violated this workflow.
+
+## Critical: Template Discovery
+
+If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+
+## CRITICAL: Mandatory Elicitation Format
+
+**When `elicit: true`, this is a HARD STOP requiring user interaction:**
+
+**YOU MUST:**
+
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. **STOP and present numbered options 1-9:**
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
+4. **WAIT FOR USER RESPONSE** - Do not proceed until user selects option or provides feedback
+
+**WORKFLOW VIOLATION:** Creating content for elicit=true sections without user interaction violates this task.
+
+**NEVER ask yes/no questions or use any other format.**
+
+## Processing Flow
+
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
+
+## Detailed Rationale Requirements
+
+When presenting section content, ALWAYS include rationale that explains:
+
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
+
+## Elicitation Results Flow
+
+After user selects elicitation method (2-9):
+
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
+
+## Agent Permissions
+
+When processing sections with agent permission fields:
+
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
+
+**For sections with restricted access:**
+
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
+
+## YOLO Mode
+
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
+
+## CRITICAL REMINDERS
+
+**❌ NEVER:**
+
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
+
+**✅ ALWAYS:**
+
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"

.claude/commands/bmad-cw/tasks/create-draft-section.md

@@ -0,0 +1,30 @@
+# /create-draft-section Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 4. Create Draft Section (Chapter)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: create-draft-section
+name: Create Draft Section
+description: Draft a complete chapter or scene using the chapter-draft-tmpl.
+persona_default: editor
+inputs:
+
+- story-outline.md | snowflake-outline.md | scene-list.md | release-plan.md
+  parameters:
+  chapter_number: integer
+  steps:
+- Extract scene beats for the chapter.
+- Draft chapter using template placeholders.
+- Highlight dialogue blocks for later polishing.
+  output: chapter-{{chapter_number}}-draft.md
+  ...

.claude/commands/bmad-cw/tasks/critical-review.md

@@ -0,0 +1,30 @@
+# /critical-review Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# Critical Review Task
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: critical-review
+name: Critical Review
+description: Comprehensive professional critique using critic-review-tmpl and rubric checklist.
+persona_default: book-critic
+inputs:
+
+- manuscript file (e.g., draft-manuscript.md or chapter file)
+  steps:
+- If audience/genre not provided, prompt user for details.
+- Read manuscript (or excerpt) for holistic understanding.
+- Fill **critic-review-tmpl** with category scores and commentary.
+- Execute **checklists/critic-rubric-checklist** to spot omissions; revise output if any boxes unchecked.
+- Present final review to user.
+  output: critic-review.md
+  ...

.claude/commands/bmad-cw/tasks/develop-character.md

@@ -0,0 +1,28 @@
+# /develop-character Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 3. Develop Character
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: develop-character
+name: Develop Character
+description: Produce rich character profiles with goals, flaws, arcs, and voice notes.
+persona_default: character-psychologist
+inputs:
+
+- concept-brief.md
+  steps:
+- Identify protagonist(s), antagonist(s), key side characters.
+- For each, fill character-profile-tmpl.
+- Offer advanced‑elicitation for each profile.
+  output: characters.md
+  ...

.claude/commands/bmad-cw/tasks/execute-checklist.md

@@ -0,0 +1,92 @@
+# /execute-checklist Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# Checklist Validation Task
+
+This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
+
+## Available Checklists
+
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-creative-writing/checklists folder to select the appropriate one to run.
+
+## Instructions
+
+1. **Initial Assessment**
+   - If user or the task being run provides a checklist name:
+     - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
+     - If multiple matches found, ask user to clarify
+     - Load the appropriate checklist from .bmad-creative-writing/checklists/
+   - If no checklist specified:
+     - Ask the user which checklist they want to use
+     - Present the available options from the files in the checklists folder
+   - Confirm if they want to work through the checklist:
+     - Section by section (interactive mode - very time consuming)
+     - All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
+
+2. **Document and Artifact Gathering**
+   - Each checklist will specify its required documents/artifacts at the beginning
+   - Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
+
+3. **Checklist Processing**
+
+   If in interactive mode:
+   - Work through each section of the checklist one at a time
+   - For each section:
+     - Review all items in the section following instructions for that section embedded in the checklist
+     - Check each item against the relevant documentation or artifacts as appropriate
+     - Present summary of findings for that section, highlighting warnings, errors and non applicable items (rationale for non-applicability).
+     - Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
+
+   If in YOLO mode:
+   - Process all sections at once
+   - Create a comprehensive report of all findings
+   - Present the complete analysis to the user
+
+4. **Validation Approach**
+
+   For each checklist item:
+   - Read and understand the requirement
+   - Look for evidence in the documentation that satisfies the requirement
+   - Consider both explicit mentions and implicit coverage
+   - Aside from this, follow all checklist llm instructions
+   - Mark items as:
+     - ✅ PASS: Requirement clearly met
+     - ❌ FAIL: Requirement not met or insufficient coverage
+     - ⚠️ PARTIAL: Some aspects covered but needs improvement
+     - N/A: Not applicable to this case
+
+5. **Section Analysis**
+
+   For each section:
+   - think step by step to calculate pass rate
+   - Identify common themes in failed items
+   - Provide specific recommendations for improvement
+   - In interactive mode, discuss findings with user
+   - Document any user decisions or explanations
+
+6. **Final Report**
+
+   Prepare a summary that includes:
+   - Overall checklist completion status
+   - Pass rates by section
+   - List of failed items with context
+   - Specific recommendations for improvement
+   - Any sections or items marked as N/A with justification
+
+## Checklist Execution Methodology
+
+Each checklist now contains embedded LLM prompts and instructions that will:
+
+1. **Guide thorough thinking** - Prompts ensure deep analysis of each section
+2. **Request specific artifacts** - Clear instructions on what documents/access is needed
+3. **Provide contextual guidance** - Section-specific prompts for better validation
+4. **Generate comprehensive reports** - Final summary with detailed findings
+
+The LLM will:
+
+- Execute the complete checklist validation
+- Present a final report with pass/fail rates and key findings
+- Offer to provide detailed analysis of any section, especially those with warnings or failures

.claude/commands/bmad-cw/tasks/expand-premise.md

@@ -0,0 +1,27 @@
+# /expand-premise Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 7. Expand Premise (Snowflake Step 2)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: expand-premise
+name: Expand Premise
+description: Turn a 1‑sentence idea into a 1‑paragraph summary.
+persona_default: plot-architect
+inputs:
+
+- premise.txt
+  steps:
+- Ask for genre confirmation.
+- Draft one paragraph (~5 sentences) covering protagonist, conflict, stakes.
+  output: premise-paragraph.md
+  ...

.claude/commands/bmad-cw/tasks/expand-synopsis.md

@@ -0,0 +1,27 @@
+# /expand-synopsis Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 8. Expand Synopsis (Snowflake Step 4)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: expand-synopsis
+name: Expand Synopsis
+description: Build a 1‑page synopsis from the paragraph summary.
+persona_default: plot-architect
+inputs:
+
+- premise-paragraph.md
+  steps:
+- Outline three‑act structure in prose.
+- Keep under 700 words.
+  output: synopsis.md
+  ...

.claude/commands/bmad-cw/tasks/final-polish.md

@@ -0,0 +1,27 @@
+# /final-polish Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 14. Final Polish
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: final-polish
+name: Final Polish
+description: Line‑edit for style, clarity, grammar.
+persona_default: editor
+inputs:
+
+- chapter-dialog.md | polished-manuscript.md
+  steps:
+- Correct grammar and tighten prose.
+- Ensure consistent voice.
+  output: chapter-final.md | final-manuscript.md
+  ...

.claude/commands/bmad-cw/tasks/generate-cover-brief.md

@@ -0,0 +1,29 @@
+# /generate-cover-brief Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# tasks/generate-cover-brief.md
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: generate-cover-brief
+name: Generate Cover Brief
+description: Interactive questionnaire that captures all creative and technical parameters for the cover.
+persona_default: cover-designer
+steps:
+
+- Ask for title, subtitle, author name, series info.
+- Ask for genre, target audience, comparable titles.
+- Ask for trim size (e.g., 6"x9"), page count, paper color.
+- Ask for mood keywords, primary imagery, color palette.
+- Ask what should appear on back cover (blurb, reviews, author bio, ISBN location).
+- Fill cover-design-brief-tmpl with collected info.
+  output: cover-brief.md
+  ...

.claude/commands/bmad-cw/tasks/generate-cover-prompts.md

@@ -0,0 +1,30 @@
+# /generate-cover-prompts Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# tasks/generate-cover-prompts.md
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: generate-cover-prompts
+name: Generate Cover Prompts
+description: Produce AI image generator prompts for front cover artwork plus typography guidance.
+persona_default: cover-designer
+inputs:
+
+- cover-brief.md
+  steps:
+- Extract mood, genre, imagery from brief.
+- Draft 3‑5 alternative stable diffusion / DALL·E prompts (include style, lens, color keywords).
+- Specify safe negative prompts.
+- Provide font pairing suggestions (Google Fonts) matching genre.
+- Output prompts and typography guidance to cover-prompts.md.
+  output: cover-prompts.md
+  ...

.claude/commands/bmad-cw/tasks/generate-scene-list.md

@@ -0,0 +1,27 @@
+# /generate-scene-list Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 10. Generate Scene List
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: generate-scene-list
+name: Generate Scene List
+description: Break synopsis into a numbered list of scenes.
+persona_default: plot-architect
+inputs:
+
+- synopsis.md | story-outline.md
+  steps:
+- Identify key beats.
+- Fill scene-list-tmpl table.
+  output: scene-list.md
+  ...

.claude/commands/bmad-cw/tasks/incorporate-feedback.md

@@ -0,0 +1,29 @@
+# /incorporate-feedback Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 6. Incorporate Feedback
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: incorporate-feedback
+name: Incorporate Feedback
+description: Merge beta feedback into manuscript; accept, reject, or revise.
+persona_default: editor
+inputs:
+
+- draft-manuscript.md
+- beta-notes.md
+  steps:
+- Summarize actionable changes.
+- Apply revisions inline.
+- Mark resolved comments.
+  output: polished-manuscript.md
+  ...

.claude/commands/bmad-cw/tasks/kb-mode-interaction.md

@@ -0,0 +1,81 @@
+# /kb-mode-interaction Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# KB Mode Interaction Task
+
+## Purpose
+
+Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.
+
+## Instructions
+
+When entering KB mode (\*kb-mode), follow these steps:
+
+### 1. Welcome and Guide
+
+Announce entering KB mode with a brief, friendly introduction.
+
+### 2. Present Topic Areas
+
+Offer a concise list of main topic areas the user might want to explore:
+
+**What would you like to know more about?**
+
+1. **Setup & Installation** - Getting started with BMad
+2. **Workflows** - Choosing the right workflow for your project
+3. **Web vs IDE** - When to use each environment
+4. **Agents** - Understanding specialized agents and their roles
+5. **Documents** - PRDs, Architecture, Stories, and more
+6. **Agile Process** - How BMad implements Agile methodologies
+7. **Configuration** - Customizing BMad for your needs
+8. **Best Practices** - Tips for effective BMad usage
+
+Or ask me about anything else related to BMad-Method!
+
+### 3. Respond Contextually
+
+- Wait for user's specific question or topic selection
+- Provide focused, relevant information from the knowledge base
+- Offer to dive deeper or explore related topics
+- Keep responses concise unless user asks for detailed explanations
+
+### 4. Interactive Exploration
+
+- After answering, suggest related topics they might find helpful
+- Maintain conversational flow rather than data dumping
+- Use examples when appropriate
+- Reference specific documentation sections when relevant
+
+### 5. Exit Gracefully
+
+When user is done or wants to exit KB mode:
+
+- Summarize key points discussed if helpful
+- Remind them they can return to KB mode anytime with \*kb-mode
+- Suggest next steps based on what was discussed
+
+## Example Interaction
+
+**User**: \*kb-mode
+
+**Assistant**: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.
+
+**What would you like to know more about?**
+
+1. **Setup & Installation** - Getting started with BMad
+2. **Workflows** - Choosing the right workflow for your project
+3. **Web vs IDE** - When to use each environment
+4. **Agents** - Understanding specialized agents and their roles
+5. **Documents** - PRDs, Architecture, Stories, and more
+6. **Agile Process** - How BMad implements Agile methodologies
+7. **Configuration** - Customizing BMad for your needs
+8. **Best Practices** - Tips for effective BMad usage
+
+Or ask me about anything else related to BMad-Method!
+
+**User**: Tell me about workflows
+
+**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]

.claude/commands/bmad-cw/tasks/outline-scenes.md

@@ -0,0 +1,27 @@
+# /outline-scenes Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 11. Outline Scenes
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: outline-scenes
+name: Outline Scenes
+description: Group scene list into chapters with act structure.
+persona_default: plot-architect
+inputs:
+
+- scene-list.md
+  steps:
+- Assign scenes to chapters.
+- Produce snowflake-outline.md with headings per chapter.
+  output: snowflake-outline.md
+  ...

.claude/commands/bmad-cw/tasks/provide-feedback.md

@@ -0,0 +1,28 @@
+# /provide-feedback Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 5. Provide Feedback (Beta)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: provide-feedback
+name: Provide Feedback (Beta)
+description: Simulate beta‑reader feedback using beta-feedback-form-tmpl.
+persona_default: beta-reader
+inputs:
+
+- draft-manuscript.md | chapter-draft.md
+  steps:
+- Read provided text.
+- Fill feedback form objectively.
+- Save as beta-notes.md or chapter-notes.md.
+  output: beta-notes.md
+  ...

.claude/commands/bmad-cw/tasks/publish-chapter.md

@@ -0,0 +1,27 @@
+# /publish-chapter Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 15. Publish Chapter
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: publish-chapter
+name: Publish Chapter
+description: Format and log a chapter release.
+persona_default: editor
+inputs:
+
+- chapter-final.md
+  steps:
+- Generate front/back matter as needed.
+- Append entry to publication-log.md (date, URL).
+  output: publication-log.md
+  ...

.claude/commands/bmad-cw/tasks/quick-feedback.md

@@ -0,0 +1,26 @@
+# /quick-feedback Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 13. Quick Feedback (Serial)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: quick-feedback
+name: Quick Feedback (Serial)
+description: Fast beta feedback focused on pacing and hooks.
+persona_default: beta-reader
+inputs:
+
+- chapter-dialog.md
+  steps:
+- Use condensed beta-feedback-form.
+  output: chapter-notes.md
+  ...

.claude/commands/bmad-cw/tasks/select-next-arc.md

@@ -0,0 +1,27 @@
+# /select-next-arc Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# ------------------------------------------------------------
+
+# 12. Select Next Arc (Serial)
+
+# ------------------------------------------------------------
+
+---
+
+task:
+id: select-next-arc
+name: Select Next Arc
+description: Choose the next 2–4‑chapter arc for serial publication.
+persona_default: plot-architect
+inputs:
+
+- retrospective data (retro.md) | snowflake-outline.md
+  steps:
+- Analyze reader feedback.
+- Update release-plan.md with upcoming beats.
+  output: release-plan.md
+  ...

.claude/commands/bmad-cw/tasks/workshop-dialog.md

@@ -0,0 +1,68 @@
+# /workshop-dialog Task
+
+When this command is used, execute the following task:
+
+<!-- Powered by BMAD™ Core -->
+
+# Workshop Dialog
+
+## Purpose
+
+Refine dialog for authenticity, character voice, and dramatic effectiveness.
+
+## Process
+
+### 1. Voice Audit
+
+For each character, assess:
+
+- Vocabulary level and word choice
+- Sentence structure preferences
+- Speech rhythms and patterns
+- Catchphrases or verbal tics
+- Educational/cultural markers
+- Emotional expression style
+
+### 2. Subtext Analysis
+
+For each exchange:
+
+- What's being said directly
+- What's really being communicated
+- Power dynamics at play
+- Emotional undercurrents
+- Character objectives
+- Obstacles to directness
+
+### 3. Flow Enhancement
+
+- Remove unnecessary dialogue tags
+- Vary attribution methods
+- Add action beats
+- Incorporate silence/pauses
+- Balance dialog with narrative
+- Ensure natural interruptions
+
+### 4. Conflict Injection
+
+Where dialog lacks tension:
+
+- Add opposing goals
+- Insert misunderstandings
+- Create subtext conflicts
+- Use indirect responses
+- Build through escalation
+- Add environmental pressure
+
+### 5. Polish Pass
+
+- Read aloud for rhythm
+- Check period authenticity
+- Verify character consistency
+- Eliminate on-the-nose dialog
+- Strengthen opening/closing lines
+- Add distinctive character markers
+
+## Output
+
+Refined dialog with stronger voices and dramatic impact