bmad-method 4.37.0 → 4.39.0

package/expansion-packs/bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml

@@ -14,7 +14,7 @@ sections:
   - id: initial-setup
     instruction: |
       This template creates comprehensive level design documentation that guides both content creation and technical implementation. This document should provide enough detail for developers to create level loading systems and for designers to create specific levels.
-      
+
       If available, review: Game Design Document (GDD), Game Architecture Document. This document should align with the game mechanics and technical systems defined in those documents.
 
   - id: introduction
@@ -22,7 +22,7 @@ sections:
     instruction: Establish the purpose and scope of level design for this game
     content: |
       This document defines the level design framework for {{game_title}}, providing guidelines for creating engaging, balanced levels that support the core gameplay mechanics defined in the Game Design Document.
-      
+
       This framework ensures consistency across all levels while providing flexibility for creative level design within established technical and design constraints.
     sections:
       - id: change-log
@@ -69,29 +69,29 @@ sections:
         title: "{{category_name}} Levels"
         template: |
           **Purpose:** {{gameplay_purpose}}
-          
+
           **Target Duration:** {{min_time}} - {{max_time}} minutes
-          
+
           **Difficulty Range:** {{difficulty_scale}}
-          
+
           **Key Mechanics Featured:**
-          
+
           - {{mechanic_1}} - {{usage_description}}
           - {{mechanic_2}} - {{usage_description}}
-          
+
           **Player Objectives:**
-          
+
           - Primary: {{primary_objective}}
           - Secondary: {{secondary_objective}}
           - Hidden: {{secret_objective}}
-          
+
           **Success Criteria:**
-          
+
           - {{completion_requirement_1}}
           - {{completion_requirement_2}}
-          
+
           **Technical Requirements:**
-          
+
           - Maximum entities: {{entity_limit}}
           - Performance target: {{fps_target}} FPS
           - Memory budget: {{memory_limit}}MB
@@ -106,11 +106,11 @@ sections:
         instruction: Based on GDD requirements, define the overall level organization
         template: |
           **Organization Type:** {{linear|hub_world|open_world}}
-          
+
           **Total Level Count:** {{number}}
-          
+
           **World Breakdown:**
-          
+
           - World 1: {{level_count}} levels - {{theme}} - {{difficulty_range}}
           - World 2: {{level_count}} levels - {{theme}} - {{difficulty_range}}
           - World 3: {{level_count}} levels - {{theme}} - {{difficulty_range}}
@@ -145,7 +145,7 @@ sections:
         instruction: Define how players access new levels
         template: |
           **Progression Gates:**
-          
+
           - Linear progression: Complete previous level
           - Star requirements: {{star_count}} stars to unlock
           - Skill gates: Demonstrate {{skill_requirement}}
@@ -160,17 +160,17 @@ sections:
         instruction: Define all environmental components that can be used in levels
         template: |
           **Terrain Types:**
-          
+
           - {{terrain_1}}: {{properties_and_usage}}
           - {{terrain_2}}: {{properties_and_usage}}
-          
+
           **Interactive Objects:**
-          
+
           - {{object_1}}: {{behavior_and_purpose}}
           - {{object_2}}: {{behavior_and_purpose}}
-          
+
           **Hazards and Obstacles:**
-          
+
           - {{hazard_1}}: {{damage_and_behavior}}
           - {{hazard_2}}: {{damage_and_behavior}}
       - id: collectibles-rewards
@@ -178,18 +178,18 @@ sections:
         instruction: Define all collectible items and their placement rules
         template: |
           **Collectible Types:**
-          
+
           - {{collectible_1}}: {{value_and_purpose}}
           - {{collectible_2}}: {{value_and_purpose}}
-          
+
           **Placement Guidelines:**
-          
+
           - Mandatory collectibles: {{placement_rules}}
           - Optional collectibles: {{placement_rules}}
           - Secret collectibles: {{placement_rules}}
-          
+
           **Reward Distribution:**
-          
+
           - Easy to find: {{percentage}}%
           - Moderate challenge: {{percentage}}%
           - High skill required: {{percentage}}%
@@ -198,18 +198,18 @@ sections:
         instruction: Define how enemies should be placed and balanced in levels
         template: |
           **Enemy Categories:**
-          
+
           - {{enemy_type_1}}: {{behavior_and_usage}}
           - {{enemy_type_2}}: {{behavior_and_usage}}
-          
+
           **Placement Principles:**
-          
+
           - Introduction encounters: {{guideline}}
           - Standard encounters: {{guideline}}
           - Challenge encounters: {{guideline}}
-          
+
           **Difficulty Scaling:**
-          
+
           - Enemy count progression: {{scaling_rule}}
           - Enemy type introduction: {{pacing_rule}}
           - Encounter complexity: {{complexity_rule}}
@@ -222,14 +222,14 @@ sections:
         title: Level Layout Principles
         template: |
           **Spatial Design:**
-          
+
           - Grid size: {{grid_dimensions}}
           - Minimum path width: {{width_units}}
           - Maximum vertical distance: {{height_units}}
           - Safe zones placement: {{safety_guidelines}}
-          
+
           **Navigation Design:**
-          
+
           - Clear path indication: {{visual_cues}}
           - Landmark placement: {{landmark_rules}}
           - Dead end avoidance: {{dead_end_policy}}
@@ -239,13 +239,13 @@ sections:
         instruction: Define how to control the rhythm and pace of gameplay within levels
         template: |
           **Action Sequences:**
-          
+
           - High intensity duration: {{max_duration}}
           - Rest period requirement: {{min_rest_time}}
           - Intensity variation: {{pacing_pattern}}
-          
+
           **Learning Sequences:**
-          
+
           - New mechanic introduction: {{teaching_method}}
           - Practice opportunity: {{practice_duration}}
           - Skill application: {{application_context}}
@@ -254,14 +254,14 @@ sections:
         instruction: Define how to create appropriate challenges for each level type
         template: |
           **Challenge Types:**
-          
+
           - Execution challenges: {{skill_requirements}}
           - Puzzle challenges: {{complexity_guidelines}}
           - Time challenges: {{time_pressure_rules}}
           - Resource challenges: {{resource_management}}
-          
+
           **Difficulty Calibration:**
-          
+
           - Skill check frequency: {{frequency_guidelines}}
           - Failure recovery: {{retry_mechanics}}
           - Hint system integration: {{help_system}}
@@ -275,7 +275,7 @@ sections:
         instruction: Define how level data should be structured for implementation
         template: |
           **Level File Format:**
-          
+
           - Data format: {{json|yaml|custom}}
           - File naming: `level_{{world}}_{{number}}.{{extension}}`
           - Data organization: {{structure_description}}
@@ -313,14 +313,14 @@ sections:
         instruction: Define how level assets are organized and loaded
         template: |
           **Tilemap Requirements:**
-          
+
           - Tile size: {{tile_dimensions}}px
           - Tileset organization: {{tileset_structure}}
           - Layer organization: {{layer_system}}
           - Collision data: {{collision_format}}
-          
+
           **Audio Integration:**
-          
+
           - Background music: {{music_requirements}}
           - Ambient sounds: {{ambient_system}}
           - Dynamic audio: {{dynamic_audio_rules}}
@@ -329,19 +329,19 @@ sections:
         instruction: Define performance requirements for level systems
         template: |
           **Entity Limits:**
-          
+
           - Maximum active entities: {{entity_limit}}
           - Maximum particles: {{particle_limit}}
           - Maximum audio sources: {{audio_limit}}
-          
+
           **Memory Management:**
-          
+
           - Texture memory budget: {{texture_memory}}MB
           - Audio memory budget: {{audio_memory}}MB
           - Level loading time: <{{load_time}}s
-          
+
           **Culling and LOD:**
-          
+
           - Off-screen culling: {{culling_distance}}
           - Level-of-detail rules: {{lod_system}}
           - Asset streaming: {{streaming_requirements}}
@@ -354,13 +354,13 @@ sections:
         title: Automated Testing
         template: |
           **Performance Testing:**
-          
+
           - Frame rate validation: Maintain {{fps_target}} FPS
           - Memory usage monitoring: Stay under {{memory_limit}}MB
           - Loading time verification: Complete in <{{load_time}}s
-          
+
           **Gameplay Testing:**
-          
+
           - Completion path validation: All objectives achievable
           - Collectible accessibility: All items reachable
           - Softlock prevention: No unwinnable states
@@ -388,14 +388,14 @@ sections:
         title: Balance Validation
         template: |
           **Metrics Collection:**
-          
+
           - Completion rate: Target {{completion_percentage}}%
           - Average completion time: {{target_time}} ± {{variance}}
           - Death count per level: <{{max_deaths}}
           - Collectible discovery rate: {{discovery_percentage}}%
-          
+
           **Iteration Guidelines:**
-          
+
           - Adjustment criteria: {{criteria_for_changes}}
           - Testing sample size: {{minimum_testers}}
           - Validation period: {{testing_duration}}
@@ -408,14 +408,14 @@ sections:
         title: Design Phase
         template: |
           **Concept Development:**
-          
+
           1. Define level purpose and goals
           2. Create rough layout sketch
           3. Identify key mechanics and challenges
           4. Estimate difficulty and duration
-          
+
           **Documentation Requirements:**
-          
+
           - Level design brief
           - Layout diagrams
           - Mechanic integration notes
@@ -424,15 +424,15 @@ sections:
         title: Implementation Phase
         template: |
           **Technical Implementation:**
-          
+
           1. Create level data file
           2. Build tilemap and layout
           3. Place entities and objects
           4. Configure level logic and triggers
           5. Integrate audio and visual effects
-          
+
           **Quality Assurance:**
-          
+
           1. Automated testing execution
           2. Internal playtesting
           3. Performance validation
@@ -441,14 +441,14 @@ sections:
         title: Integration Phase
         template: |
           **Game Integration:**
-          
+
           1. Level progression integration
           2. Save system compatibility
           3. Analytics integration
           4. Achievement system integration
-          
+
           **Final Validation:**
-          
+
           1. Full game context testing
           2. Performance regression testing
           3. Platform compatibility verification
@@ -481,4 +481,4 @@ sections:
           - Difficulty curve adherence: {{curve_accuracy}}
           - Mechanic integration effectiveness: {{integration_score}}
           - Player guidance clarity: {{guidance_score}}
-          - Content accessibility: {{accessibility_rate}}%
+          - Content accessibility: {{accessibility_rate}}%

package/expansion-packs/bmad-2d-unity-game-dev/workflows/game-dev-greenfield.yaml

@@ -17,21 +17,21 @@ workflow:
         - brainstorming_session
         - game_research_prompt
         - player_research
-      notes: 'Start with brainstorming game concepts, then create comprehensive game brief. SAVE OUTPUT: Copy final game-brief.md to your project''s docs/design/ folder.'
+      notes: "Start with brainstorming game concepts, then create comprehensive game brief. SAVE OUTPUT: Copy final game-brief.md to your project's docs/design/ folder."
     - agent: game-designer
       creates: game-design-doc.md
       requires: game-brief.md
       optional_steps:
         - competitive_analysis
         - technical_research
-      notes: 'Create detailed Game Design Document using game-design-doc-tmpl. Defines all gameplay mechanics, progression, and technical requirements. SAVE OUTPUT: Copy final game-design-doc.md to your project''s docs/design/ folder.'
+      notes: "Create detailed Game Design Document using game-design-doc-tmpl. Defines all gameplay mechanics, progression, and technical requirements. SAVE OUTPUT: Copy final game-design-doc.md to your project's docs/design/ folder."
     - agent: game-designer
       creates: level-design-doc.md
       requires: game-design-doc.md
       optional_steps:
         - level_prototyping
         - difficulty_analysis
-      notes: 'Create level design framework using level-design-doc-tmpl. Establishes content creation guidelines and performance requirements. SAVE OUTPUT: Copy final level-design-doc.md to your project''s docs/design/ folder.'
+      notes: "Create level design framework using level-design-doc-tmpl. Establishes content creation guidelines and performance requirements. SAVE OUTPUT: Copy final level-design-doc.md to your project's docs/design/ folder."
     - agent: solution-architect
       creates: game-architecture.md
       requires:
@@ -41,7 +41,7 @@ workflow:
         - technical_research_prompt
         - performance_analysis
         - platform_research
-      notes: 'Create comprehensive technical architecture using game-architecture-tmpl. Defines Unity systems, performance optimization, and code structure. SAVE OUTPUT: Copy final game-architecture.md to your project''s docs/architecture/ folder.'
+      notes: "Create comprehensive technical architecture using game-architecture-tmpl. Defines Unity systems, performance optimization, and code structure. SAVE OUTPUT: Copy final game-architecture.md to your project's docs/architecture/ folder."
     - agent: game-designer
       validates: design_consistency
       requires: all_design_documents
@@ -66,7 +66,7 @@ workflow:
       optional_steps:
         - quick_brainstorming
         - concept_validation
-      notes: 'Create focused game brief for prototype. Emphasize core mechanics and immediate playability. SAVE OUTPUT: Copy final game-brief.md to your project''s docs/ folder.'
+      notes: "Create focused game brief for prototype. Emphasize core mechanics and immediate playability. SAVE OUTPUT: Copy final game-brief.md to your project's docs/ folder."
     - agent: game-designer
       creates: prototype-design.md
       uses: create-doc prototype-design OR create-game-story

package/expansion-packs/bmad-2d-unity-game-dev/workflows/game-prototype.yaml

@@ -44,7 +44,7 @@ workflow:
       notes: Implement stories in priority order. Test frequently in the Unity Editor and adjust design based on what feels fun. Document discoveries.
   workflow_end:
     action: prototype_evaluation
-    notes: 'Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive.'
+    notes: "Prototype complete. Evaluate core mechanics, gather feedback, and decide next steps: iterate, expand, or archive."
   game_jam_sequence:
     - step: jam_concept
       agent: game-designer

package/expansion-packs/bmad-creative-writing/README.md

@@ -0,0 +1,132 @@
+# BMad Creative Writing Expansion Pack
+
+Transform your AI into a complete creative writing studio with specialized agents for fiction, screenwriting, and narrative design.
+
+## 📚 Overview
+
+The Creative Writing Expansion Pack extends BMad-Method with a comprehensive suite of writing-focused agents, workflows, and tools. Whether you're crafting novels, screenplays, short stories, or interactive narratives, this pack provides structured AI assistance throughout your creative process.
+
+### Key Features
+- 🤖 **10 Specialized Writing Agents** - From plot architecture to dialogue refinement
+- 📖 **8 Complete Workflows** - Novel writing, screenplay development, series planning, and more
+- ✅ **27 Quality Checklists** - Genre-specific and technical quality assurance
+- 📝 **22 Writing Tasks** - Structured activities for every phase of writing
+- 🎭 **8 Professional Templates** - Character profiles, story outlines, world guides
+
+## ✍️ Included Agents
+
+### Core Writing Team
+1. **Plot Architect** - Story structure, pacing, and narrative arc design
+2. **Character Psychologist** - Deep character development and psychology
+3. **World Builder** - Setting, universe, and environment creation
+4. **Editor** - Style, grammar, consistency, and flow refinement
+5. **Beta Reader** - First reader perspective and feedback simulation
+
+### Specialist Agents
+6. **Dialog Specialist** - Natural dialogue, voice, and conversation crafting
+7. **Narrative Designer** - Interactive storytelling and branching narratives
+8. **Genre Specialist** - Genre conventions, tropes, and market awareness
+9. **Book Critic** - Professional literary analysis and review
+10. **Cover Designer** - Book cover concepts and visual storytelling
+
+## 🚀 Installation
+
+### Via BMad Installer (After PR Acceptance)
+```bash
+npx bmad-method install
+# Select "Creative Writing Studio" from the expansion packs list
+```
+
+### Manual Installation
+1. Clone or download this expansion pack
+2. Copy to your BMad Method installation:
+   ```bash
+   cp -r bmad-creative-writing/* ~/bmad-method/expansion-packs/bmad-creative-writing/
+   ```
+3. Run the BMad installer to register the pack
+
+## 💡 Usage
+
+### Quick Start
+```bash
+# Load the complete creative writing team
+bmad load team creative-writing
+
+# Or activate individual agents
+bmad activate plot-architect
+bmad activate character-psychologist
+```
+
+### Available Workflows
+- **novel-writing** - Complete novel development from premise to manuscript
+- **screenplay-development** - Three-act screenplay with industry formatting
+- **short-story-creation** - Focused narrative for magazines/anthologies
+- **series-planning** - Multi-book series architecture and continuity
+
+## 📋 Key Components
+
+### Templates
+- `character-profile-tmpl.yaml` - Comprehensive character development
+- `story-outline-tmpl.yaml` - Three-act structure planning
+- `world-guide-tmpl.yaml` - World-building documentation
+- `scene-list-tmpl.yaml` - Scene-by-scene breakdown
+- `chapter-draft-tmpl.yaml` - Chapter structure template
+- `premise-brief-tmpl.yaml` - Story concept development
+- `beta-feedback-form.yaml` - Structured reader feedback
+- `cover-design-brief-tmpl.yaml` - Cover concept specifications
+
+### Featured Checklists
+- Genre-specific: Fantasy, Sci-Fi, Romance, Mystery, Thriller, Horror
+- Technical: Plot structure, character consistency, timeline continuity
+- Publishing: KDP-ready, eBook formatting, marketing copy
+- Quality: Scene quality, dialogue authenticity, pacing/stakes
+
+## 🎯 Use Cases
+
+### Novel Writing
+- Premise development and market positioning
+- Three-act structure with subplot integration
+- Character arc tracking across chapters
+- Beta feedback simulation before human readers
+
+### Screenplay Development
+- Industry-standard formatting
+- Visual storytelling emphasis
+- Dialogue-driven narrative
+- Scene/location optimization
+
+### Series Planning
+- Multi-book continuity management
+- Character evolution across volumes
+- World expansion strategies
+- Reader retention hooks
+
+### Publishing Preparation
+- KDP package assembly
+- Cover design briefs
+- Marketing copy generation
+- Genre positioning
+
+## 🤝 Contributing
+
+We welcome contributions! Please:
+1. Fork the repository
+2. Create a feature branch
+3. Follow BMad Method conventions
+4. Submit a PR with clear description
+
+## 📄 License
+
+This expansion pack follows the same license as BMad Method core.
+
+## 🙏 Credits
+
+Created by Wes for the BMad Method community.
+
+Special thanks to Brian (BMad) for creating the BMad Method framework.
+
+---
+
+**Version:** 1.0.0  
+**Compatible with:** BMad Method v1.0+  
+**Last Updated:** 2024

package/expansion-packs/bmad-creative-writing/agent-teams/agent-team.yaml

@@ -0,0 +1,19 @@
+bundle:
+  name: Creative Writing Team
+  icon: ✍️
+  description: Complete creative writing team for fiction, narrative design, and storytelling projects
+agents:
+  - plot-architect
+  - character-psychologist
+  - world-builder
+  - editor
+  - beta-reader
+  - dialog-specialist
+  - narrative-designer
+  - genre-specialist
+  - book-critic  # newly added professional critic agent
+workflows:
+  - novel-writing
+  - screenplay-development
+  - short-story-creation
+  - series-planning

package/expansion-packs/bmad-creative-writing/agents/beta-reader.md

@@ -0,0 +1,91 @@
+# beta-reader
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to {root}/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → {root}/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Greet user with your name/role and mention `*help` command
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Beta Reader
+  id: beta-reader
+  title: Reader Experience Simulator
+  icon: 👓
+  whenToUse: Use for reader perspective, plot hole detection, confusion points, and engagement analysis
+  customization: null
+persona:
+  role: Advocate for the reader's experience
+  style: Honest, constructive, reader-focused, intuitive
+  identity: Simulates target audience reactions and identifies issues
+  focus: Ensuring story resonates with intended readers
+core_principles:
+  - Reader confusion is author's responsibility
+  - First impressions matter
+  - Emotional engagement trumps technical perfection
+  - Plot holes break immersion
+  - Promises made must be kept
+  - Numbered Options Protocol - Always use numbered lists for user selections
+commands:
+  - "*help - Show numbered list of available commands for selection"
+  - "*first-read - Simulate first-time reader experience"
+  - "*plot-holes - Identify logical inconsistencies"
+  - "*confusion-points - Flag unclear sections"
+  - "*engagement-curve - Map reader engagement"
+  - "*promise-audit - Check setup/payoff balance"
+  - "*genre-expectations - Verify genre satisfaction"
+  - "*emotional-impact - Assess emotional resonance"
+  - "*yolo - Toggle Yolo Mode"
+  - "*exit - Say goodbye as the Beta Reader, and then abandon inhabiting this persona"
+dependencies:
+  tasks:
+    - create-doc.md
+    - provide-feedback.md
+    - quick-feedback.md
+    - analyze-reader-feedback.md
+    - execute-checklist.md
+    - advanced-elicitation.md
+  templates:
+    - beta-feedback-form.yaml
+  checklists:
+    - beta-feedback-closure-checklist.md
+  data:
+    - bmad-kb.md
+    - story-structures.md
+```
+
+## Startup Context
+
+You are the Beta Reader, the story's first audience. You experience the narrative as readers will, catching issues that authors are too close to see.
+
+Monitor:
+- **Confusion triggers**: unclear motivations, missing context
+- **Engagement valleys**: where attention wanders
+- **Logic breaks**: plot holes and inconsistencies
+- **Promise violations**: setups without payoffs
+- **Pacing issues**: rushed or dragging sections
+- **Emotional flat spots**: where impact falls short
+
+Read with fresh eyes and an open heart.
+
+Remember to present all options as numbered lists for easy selection.

package/expansion-packs/bmad-creative-writing/agents/book-critic.md

@@ -0,0 +1,35 @@
+# Book Critic Agent Definition
+# -------------------------------------------------------
+```yaml
+agent:
+  name: Evelyn Clarke
+  id: book-critic
+  title: Renowned Literary Critic
+  icon: 📚
+  whenToUse: Use to obtain a thorough, professional review of a finished manuscript or chapter, including holistic and category‑specific ratings with detailed rationale.
+  customization: null
+persona:
+  role: Widely Respected Professional Book Critic
+  style: Incisive, articulate, context‑aware, culturally attuned, fair but unflinching
+  identity: Internationally syndicated critic known for balancing scholarly insight with mainstream readability
+  focus: Evaluating manuscripts against reader expectations, genre standards, market competition, and cultural zeitgeist
+  core_principles:
+    - Audience Alignment – Judge how well the work meets the needs and tastes of its intended readership
+    - Genre Awareness – Compare against current and classic exemplars in the genre
+    - Cultural Relevance – Consider themes in light of present‑day conversations and sensitivities
+    - Critical Transparency – Always justify scores with specific textual evidence
+    - Constructive Insight – Highlight strengths as well as areas for growth
+    - Holistic & Component Scoring – Provide overall rating plus sub‑ratings for plot, character, prose, pacing, originality, emotional impact, and thematic depth
+startup:
+  - Greet the user, explain ratings range (e.g., 1–10 or A–F), and list sub‑rating categories.
+  - Remind user to specify target audience and genre if not already provided.
+commands:
+  - help: Show available commands
+  - critique {file|text}: Provide full critical review with ratings and rationale (default)
+  - quick-take {file|text}: Short paragraph verdict with overall rating only
+  - exit: Say goodbye as the Book Critic and abandon persona
+dependencies:
+  tasks:
+    - critical-review               # ensure this task exists; otherwise agent handles logic inline
+  checklists:
+    - genre-tropes-checklist        # optional, enhances genre comparison