feat: Refine WeChat mini-game workflows and documentation
This commit refines the development workflows in the `bmad-wechat-mini-game-dev` expansion pack to align with user feedback and the newly established agent roles.
The following changes have been made:
1. **Updated Greenfield Workflow:**
- The `game-dev-greenfield.yaml` workflow has been updated to a new, more structured planning sequence: `game-analyst` -> `game-pm` -> `game-designer` -> `game-orchestrator` -> `game-po`.
- The corresponding Mermaid diagram has been updated to visually represent this new process.
2. **Streamlined Prototype Workflow:**
- The `game-prototype.yaml` workflow has been simplified to better support rapid, iterative prototyping.
- The Mermaid diagram for the prototype workflow has also been updated.
These changes make the workflows more specific, structured, and better aligned with the specialized agent roles in the team, fulfilling the user's request for a more optimized development process.
This commit is contained in:
parent
7d66ac29db
commit
f9da9eb35f
|
|
@ -12,74 +12,52 @@ workflow:
|
||||||
- prototype-game
|
- prototype-game
|
||||||
- game-jam
|
- game-jam
|
||||||
full_game_sequence:
|
full_game_sequence:
|
||||||
- agent: game-designer
|
- agent: game-analyst
|
||||||
creates: game-brief.md
|
creates: game-brief.md
|
||||||
optional_steps:
|
optional_steps:
|
||||||
- brainstorming_session
|
- brainstorming_session
|
||||||
- game_research_prompt
|
- market_research
|
||||||
- player_research
|
notes: "The Analyst creates the initial Game Brief, defining the core concept and market opportunity."
|
||||||
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-pm
|
||||||
|
creates: prd.md
|
||||||
|
requires: game-brief.md
|
||||||
|
notes: "The Project Manager expands the brief into a full Product Requirements Document (PRD), defining features, epics, and user stories."
|
||||||
- agent: game-designer
|
- agent: game-designer
|
||||||
creates: game-design-doc.md
|
creates: game-design-doc.md
|
||||||
requires: game-brief.md
|
requires: prd.md
|
||||||
optional_steps:
|
notes: "The Game Designer uses the PRD to create a detailed Game Design Document (GDD), focusing on mechanics, game feel, and player experience."
|
||||||
- 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."
|
|
||||||
- agent: game-qa
|
|
||||||
validates: gdd_testability
|
|
||||||
requires: game-design-doc.md
|
|
||||||
optional_steps:
|
|
||||||
- risk_assessment
|
|
||||||
notes: "(Optional but Recommended) The QA agent reviews the GDD for testability, clarity, and potential performance risks."
|
|
||||||
- agent: game-orchestrator
|
- agent: game-orchestrator
|
||||||
creates: game-architecture.md
|
creates: game-architecture.md
|
||||||
requires: game-design-doc.md
|
|
||||||
optional_steps:
|
|
||||||
- technical_research_prompt
|
|
||||||
- performance_analysis
|
|
||||||
- platform_research
|
|
||||||
notes: "Create comprehensive technical architecture using game-architecture-tmpl. Defines WeChat Mini-Game systems, performance optimization, and code structure. SAVE OUTPUT: Copy final game-architecture.md to your project's docs/architecture/ folder."
|
|
||||||
- agent: game-pm
|
|
||||||
creates: project-plan.md
|
|
||||||
requires:
|
requires:
|
||||||
|
- prd.md
|
||||||
- game-design-doc.md
|
- game-design-doc.md
|
||||||
- game-architecture.md
|
notes: "The Orchestrator creates the technical architecture to support the GDD and PRD."
|
||||||
notes: "The PM creates a high-level project plan, including timelines, milestones, and epics, based on the GDD and architecture."
|
|
||||||
- agent: game-po
|
- agent: game-po
|
||||||
validates: all_documents
|
action: shard_documents
|
||||||
requires:
|
requires:
|
||||||
- game-brief.md
|
- prd.md
|
||||||
- game-design-doc.md
|
- game-design-doc.md
|
||||||
- game-architecture.md
|
- game-architecture.md
|
||||||
- project-plan.md
|
notes: "The Product Owner shards the final documents into epics and stories for the development team."
|
||||||
uses: game-design-checklist
|
|
||||||
notes: The Product Owner validates all planning documents for consistency, completeness, and alignment with the project's goals.
|
|
||||||
- agent: various
|
|
||||||
updates: flagged_design_documents
|
|
||||||
condition: validation_issues
|
|
||||||
notes: If validation finds issues, return to the relevant agent to fix and re-export the updated documents to the docs/ folder.
|
|
||||||
project_setup_guidance:
|
project_setup_guidance:
|
||||||
action: guide_game_project_structure
|
action: guide_game_project_structure
|
||||||
notes: Set up the game project structure following the game architecture document. Create pages/, components/, js/, and images/ directories. Initialize WeChat Mini-Game configuration.
|
notes: Set up the game project structure following the game architecture document. Create pages/, components/, js/, and images/ directories. Initialize WeChat Mini-Game configuration.
|
||||||
workflow_end:
|
workflow_end:
|
||||||
action: move_to_story_development
|
action: move_to_story_development
|
||||||
notes: All planning artifacts are complete. Begin the story-driven development phase. Use the Game Scrum Master to create implementation stories from the design documents.
|
notes: All planning artifacts are complete and sharded. Begin the story-driven development phase.
|
||||||
prototype_sequence:
|
prototype_sequence:
|
||||||
- step: prototype_scope
|
- step: prototype_scope
|
||||||
action: assess_prototype_complexity
|
agent: game-analyst
|
||||||
notes: First, assess if this needs a full game design (use full_game_sequence) or can be a rapid prototype.
|
action: assess_prototype_scope
|
||||||
- agent: game-designer
|
notes: "The Analyst quickly defines the core concept and scope for a prototype."
|
||||||
creates: game-brief.md
|
|
||||||
optional_steps:
|
|
||||||
- quick_brainstorming
|
|
||||||
- concept_validation
|
|
||||||
notes: "Create a focused game brief for the prototype. Emphasize core mechanics and immediate playability. SAVE OUTPUT: Copy final game-brief.md to your project's docs/ folder."
|
|
||||||
- agent: game-designer
|
- agent: game-designer
|
||||||
creates: prototype-design.md
|
creates: prototype-design.md
|
||||||
uses: create-doc prototype-design OR create-game-story
|
requires: concept-summary.md
|
||||||
requires: game-brief.md
|
notes: "The Designer creates a minimal design spec for the core mechanic."
|
||||||
notes: Create a minimal design document or jump directly to implementation stories for rapid prototyping. Choose based on the prototype's complexity.
|
- agent: game-developer
|
||||||
|
action: implement_prototype
|
||||||
|
requires: prototype-design.md
|
||||||
|
notes: "The Developer rapidly implements the core mechanic for playtesting."
|
||||||
prototype_workflow_end:
|
prototype_workflow_end:
|
||||||
action: move_to_rapid_implementation
|
action: move_to_rapid_implementation
|
||||||
notes: The prototype is defined. Begin immediate implementation with the Game Developer. Focus on core mechanics first, then iterate based on playtesting.
|
notes: The prototype is defined. Begin immediate implementation with the Game Developer. Focus on core mechanics first, then iterate based on playtesting.
|
||||||
|
|
@ -87,35 +65,29 @@ workflow:
|
||||||
```mermaid
|
```mermaid
|
||||||
graph TD
|
graph TD
|
||||||
A[Start: WeChat Game Development Project] --> B{Project Scope?}
|
A[Start: WeChat Game Development Project] --> B{Project Scope?}
|
||||||
B -->|Full Game/Production| C[game-designer: game-brief.md]
|
B -->|Full Game/Production| C[game-analyst: game-brief.md]
|
||||||
B -->|Prototype/Game Jam| D[game-designer: focused game-brief.md]
|
B -->|Prototype/Game Jam| D[game-analyst: prototype-scope.md]
|
||||||
|
|
||||||
C --> E[game-designer: game-design-doc.md]
|
C --> E[game-pm: prd.md]
|
||||||
E --> F{QA Review? (Optional)}
|
E --> F[game-designer: game-design-doc.md]
|
||||||
F -->|Yes| G[game-qa: GDD Testability Review]
|
F --> G[game-orchestrator: game-architecture.md]
|
||||||
F -->|No| H[game-orchestrator: game-architecture.md]
|
G --> H[game-po: Shard Documents]
|
||||||
G --> H
|
H --> I[Move to Story Development Phase]
|
||||||
H --> I[game-pm: project-plan.md]
|
|
||||||
I --> J[game-po: Validate All Documents]
|
|
||||||
J --> K{Validation Issues?}
|
|
||||||
K -->|Yes| L[Return to relevant agent for fixes]
|
|
||||||
K -->|No| M[Set up game project structure]
|
|
||||||
L --> J
|
|
||||||
M --> N[Move to Story Development Phase]
|
|
||||||
|
|
||||||
D --> O[game-designer: prototype-design.md]
|
D --> J[game-designer: prototype-design.md]
|
||||||
O --> P[Move to Rapid Implementation]
|
J --> K[game-developer: Implement Prototype]
|
||||||
|
K --> L[Prototype Evaluation & Iteration]
|
||||||
|
|
||||||
style N fill:#90EE90
|
style I fill:#90EE90
|
||||||
style P fill:#90EE90
|
style L fill:#90EE90
|
||||||
style C fill:#FFE4B5
|
style C fill:#FFE4B5
|
||||||
style E fill:#FFE4B5
|
style E fill:#ADD8E6
|
||||||
|
style F fill:#E6E6FA
|
||||||
style G fill:#FFDAB9
|
style G fill:#FFDAB9
|
||||||
style H fill:#E6E6FA
|
style H fill:#FFB6C1
|
||||||
style I fill:#ADD8E6
|
|
||||||
style J fill:#FFB6C1
|
|
||||||
style D fill:#FFB6C1
|
style D fill:#FFB6C1
|
||||||
style O fill:#FFB6C1
|
style J fill:#FFB6C1
|
||||||
|
style K fill:#FFB6C1
|
||||||
```
|
```
|
||||||
decision_guidance:
|
decision_guidance:
|
||||||
use_full_sequence_when:
|
use_full_sequence_when:
|
||||||
|
|
|
||||||
|
|
@ -13,44 +13,28 @@ workflow:
|
||||||
- rapid-iteration
|
- rapid-iteration
|
||||||
prototype_sequence:
|
prototype_sequence:
|
||||||
- step: concept_definition
|
- step: concept_definition
|
||||||
agent: game-designer
|
agent: game-analyst
|
||||||
duration: 15-30 minutes
|
duration: 15-30 minutes
|
||||||
creates: concept-summary.md
|
creates: concept-summary.md
|
||||||
notes: Quickly define core game concept, primary mechanic, and target experience. Focus on what makes this game unique and fun.
|
notes: "The Analyst quickly defines the core concept, target experience, and success criteria for the prototype."
|
||||||
- step: rapid_design
|
- step: rapid_design
|
||||||
agent: game-designer
|
agent: game-designer
|
||||||
duration: 30-60 minutes
|
duration: 30-60 minutes
|
||||||
creates: prototype-spec.md
|
creates: prototype-spec.md
|
||||||
requires: concept-summary.md
|
requires: concept-summary.md
|
||||||
optional_steps:
|
notes: "The Designer creates a minimal design spec, focusing on the core mechanic and controls."
|
||||||
- quick_brainstorming
|
- step: implementation
|
||||||
- reference_research
|
|
||||||
notes: Create minimal but complete design specification. Focus on core mechanics, basic controls, and success/failure conditions.
|
|
||||||
- step: technical_planning
|
|
||||||
agent: game-developer
|
|
||||||
duration: 15-30 minutes
|
|
||||||
creates: prototype-architecture.md
|
|
||||||
requires: prototype-spec.md
|
|
||||||
notes: Define a minimal technical implementation plan. Identify the core WeChat Mini-Game systems needed and any performance constraints.
|
|
||||||
- step: implementation_stories
|
|
||||||
agent: game-sm
|
|
||||||
duration: 30-45 minutes
|
|
||||||
creates: prototype-stories/
|
|
||||||
requires:
|
|
||||||
- prototype-spec.md
|
|
||||||
- prototype-architecture.md
|
|
||||||
notes: Create 3-5 focused implementation stories for the core prototype features. Each story should be completable in 2-4 hours.
|
|
||||||
- step: iterative_development
|
|
||||||
agent: game-developer
|
agent: game-developer
|
||||||
duration: varies
|
duration: varies
|
||||||
implements: prototype-stories/
|
creates: working-prototype
|
||||||
notes: Implement stories in priority order. Test frequently and adjust the design based on what feels fun. Document discoveries.
|
requires: prototype-spec.md
|
||||||
|
notes: "The Developer directly implements the core mechanic for rapid playtesting and iteration. No formal stories are created."
|
||||||
- step: qa_check
|
- step: qa_check
|
||||||
agent: game-qa
|
agent: game-qa
|
||||||
duration: 15-30 minutes
|
duration: 15-30 minutes
|
||||||
optional: true
|
optional: true
|
||||||
requires: working-prototype
|
requires: working-prototype
|
||||||
notes: "(Optional) Perform a quick QA check to ensure the prototype is stable enough for effective playtesting and feedback."
|
notes: "(Optional) Perform a quick stability check to ensure the prototype is usable for feedback sessions."
|
||||||
workflow_end:
|
workflow_end:
|
||||||
action: prototype_evaluation
|
action: prototype_evaluation
|
||||||
notes: "Prototype complete. Evaluate the core mechanics, gather feedback, and decide on the next steps: iterate, expand, or archive."
|
notes: "Prototype complete. Evaluate the core mechanics, gather feedback, and decide on the next steps: iterate, expand, or archive."
|
||||||
|
|
@ -73,31 +57,27 @@ workflow:
|
||||||
```mermaid
|
```mermaid
|
||||||
graph TD
|
graph TD
|
||||||
A[Start: Prototype Project] --> B{Development Context?}
|
A[Start: Prototype Project] --> B{Development Context?}
|
||||||
B -->|Standard Prototype| C[game-designer: concept-summary.md]
|
B -->|Standard Prototype| C[game-analyst: concept-summary.md]
|
||||||
B -->|Game Jam| D[game-designer: jam-concept.md]
|
B -->|Game Jam| D[game-designer: jam-concept.md]
|
||||||
|
|
||||||
C --> E[game-designer: prototype-spec.md]
|
C --> E[game-designer: prototype-spec.md]
|
||||||
E --> F[game-developer: prototype-architecture.md]
|
E --> F[game-developer: implementation]
|
||||||
F --> G[game-sm: create prototype stories]
|
F --> G{QA Check? (Optional)}
|
||||||
G --> H[game-developer: iterative implementation]
|
G -->|Yes| H[game-qa: Stability Check]
|
||||||
H --> I{QA Check? (Optional)}
|
G -->|No| I[Prototype Evaluation]
|
||||||
I -->|Yes| J[game-qa: Stability Check]
|
H --> I
|
||||||
I -->|No| K[Prototype Evaluation]
|
|
||||||
J --> K
|
|
||||||
|
|
||||||
D --> L[game-developer: direct implementation]
|
D --> J[game-developer: direct implementation]
|
||||||
L --> M[Game Jam Submission]
|
J --> K[Game Jam Submission]
|
||||||
|
|
||||||
|
style I fill:#90EE90
|
||||||
style K fill:#90EE90
|
style K fill:#90EE90
|
||||||
style M fill:#90EE90
|
|
||||||
style C fill:#FFE4B5
|
style C fill:#FFE4B5
|
||||||
style E fill:#FFE4B5
|
style E fill:#FFE4B5
|
||||||
style F fill:#FFE4B5
|
style F fill:#FFE4B5
|
||||||
style G fill:#FFE4B5
|
style H fill:#FFDAB9
|
||||||
style H fill:#FFE4B5
|
|
||||||
style J fill:#FFDAB9
|
|
||||||
style D fill:#FFB6C1
|
style D fill:#FFB6C1
|
||||||
style L fill:#FFB6C1
|
style J fill:#FFB6C1
|
||||||
```
|
```
|
||||||
decision_guidance:
|
decision_guidance:
|
||||||
use_prototype_sequence_when:
|
use_prototype_sequence_when:
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue