name: 'step-09-complete' description: 'Complete the architecture workflow with final review and handoff guidance'

Path Definitions

workflow_path: '{installed_path}'

File References

thisStepFile: './step-09-complete.md' workflowFile: '{workflow_path}/workflow.md' outputFile: '{output_folder}/game-architecture.md'

Handoff References

epicWorkflow: 'skill:gds-create-epics-and-stories'

projectContextWorkflow: 'skill:gds-generate-project-context'

Step 9: Completion

Progress: Step 9 of 9 - Architecture Complete!

STEP GOAL:

Generate the executive summary, finalize the document, update workflow status, and provide clear handoff guidance for the next workflow phase.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

NEVER generate content without user input
CRITICAL: Read the complete step file before taking any action
YOU ARE A FACILITATOR, not a content generator
NEVER mention time estimates
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config {communication_language}

Role Reinforcement:

You are a veteran game architect facilitator
This is the final step - ensure completeness
Provide actionable next steps

Step-Specific Rules:

Generate executive summary from all content
Ensure document is ready for AI agent consumption
Provide clear implementation guidance

EXECUTION PROTOCOLS:

Show your analysis before taking any action
Generate final sections
Update frontmatter stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]
Present completion summary and next steps

Sequence of Instructions (Do not deviate, skip, or optimize)

1. Generate Executive Summary

Create summary from all sections:

Based on all documented content, synthesize an executive summary:

## Executive Summary

**{{game_name}}** architecture is designed for {{engine}} targeting {{platform}}.

**Key Architectural Decisions:**

- {{decision_1_summary}}
- {{decision_2_summary}}
- {{decision_3_summary}}

**Project Structure:** {{organization_pattern}} organization with {{system_count}} core systems.

**Implementation Patterns:** {{pattern_count}} patterns defined ensuring AI agent consistency.

**Ready for:** Epic implementation phase

2. Generate Development Setup Section

"Let me generate the development environment setup section.

Development Prerequisites:

## Development Environment

### Prerequisites

{{prerequisites_list}}

### AI Tooling (MCP Servers)

{{if_mcps_selected}}
The following MCP servers were selected during architecture to enhance AI-assisted development:

| MCP Server | Purpose | Install Type |
| ---------- | ------- | ------------ |
{{mcp_table_rows}}

**Setup:**
{{mcp_setup_instructions}}

These give your AI assistant direct access to {{engine}} for scene inspection, asset queries, and context-aware code generation.
{{else}}
No engine-specific MCP servers were selected. You can add them later by searching for "{{engine}} MCP server" to find available integrations.
{{/if_mcps_selected}}

### Setup Commands

```bash
{{setup_commands}}
```

First Steps

{{first_step}}
{{second_step}}
Configure MCP servers (if selected) per the AI Tooling instructions above


Does this capture the setup process correctly?"

### 3. Finalize Document

**Update the document with final content:**

- Add Executive Summary at the top (after frontmatter)
- Add Development Environment section
- Update document status to 'complete'
- Update frontmatter with all steps completed

**Final frontmatter:**

```yaml
---
title: 'Game Architecture'
project: '{{project_name}}'
date: '{{date}}'
author: '{{user_name}}'
version: '1.0'
stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]
status: 'complete'
engine: '{{engine}}'
platform: '{{platform}}'
---

4. Update Workflow Status

If not in standalone mode:

Load {output_folder}/gds-workflow-status.yaml and:

Update create-architecture status to the output file path
Preserve all comments and structure
Determine next workflow in sequence

5. Present Completion Summary

"Architecture Complete!

{{user_name}}, the Game Architecture for {{game_name}} is now complete!

Architecture Summary:

Engine: {{engine}} v{{version}}
Platform: {{platform}}
Organization: {{organization_pattern}}
Decisions Made: {{decision_count}}
Patterns Defined: {{pattern_count}}

Sections Completed:

Project Context
Engine & Framework
Architectural Decisions
Cross-cutting Concerns
Project Structure
Implementation Patterns
Validation
Development Setup

Document saved to: {outputFile}

Do you want to review or adjust anything before we finalize?

Optional Enhancement: Project Context File

Would you like to create a project-context.md file? This is a concise, optimized guide for AI agents that captures:

Critical engine-specific rules they might miss
Specific patterns and conventions for your game project
Performance and optimization requirements
Anti-patterns and edge cases to avoid

{if_existing_project_context} I noticed you already have a project context file. Would you like to update it with your new architectural decisions? {else} This file helps ensure AI agents implement game code consistently with your project's unique requirements and patterns. {/if_existing_project_context}

Create/Update project context? [Y/N]"

6. Handle Project Context Creation Choice

If user responds 'Y' or 'yes' to creating/updating project context:

"Excellent choice! Let me launch the Generate Project Context workflow to create a comprehensive guide for AI agents.

This will help ensure consistent implementation by capturing:

Engine-specific patterns and rules
Performance and optimization conventions from your architecture
Testing and quality standards
Anti-patterns to avoid

The workflow will collaborate with you to create an optimized project-context.md file that AI agents will read before implementing any game code."

Execute the Generate Project Context workflow:

Load and execute: {projectContextWorkflow}
The workflow will handle discovery, generation, and completion of the project context file
After completion, return here for final handoff

If user responds 'N' or 'no': "Understood! Your architecture is complete and ready for implementation. You can always create a project context file later using the Generate Project Context workflow if needed."

7. Handle Review Requests

If user wants to review:

"Which section would you like to review?

Executive Summary
Engine & Framework
Architectural Decisions
Cross-cutting Concerns
Project Structure
Implementation Patterns
Validation Summary
Development Setup

Or type 'all' to see the complete document."

Show requested section and allow edits.

8. Present Next Steps Menu

After user confirms completion:

"Recommended Next Steps for {{game_name}}:

Initialize Project - Run the setup commands to create your project
- Command: {{setup_command}}
- This creates the base structure we designed
Create Epics - Break down GDD into implementation epics
- Workflow: create-epics
- Input: GDD + Architecture
- Output: Implementation-ready epic stories
Begin Implementation - Start coding with AI agents
- Each agent will read this architecture
- Patterns ensure consistency across all code

Which would you like to do next?

Review the completed architecture
Proceed to Epic creation workflow
Exit workflow"

9. Handle User Selection

Based on user choice:

If 1 (Review):

Present full document or requested section
Return to next steps menu

If 2 (Epic Creation):

Confirm architecture is saved
Provide handoff guidance for epic workflow
Note that architecture document will be input

If 3 (Exit):

Confirm document is saved and complete
Exit workflow gracefully

10. Provide Handoff Guidance

For Epic Creation handoff:

"Handoff to Epic Creation

Your architecture is ready to guide epic creation.

What the Epic workflow will do:

Read your architecture document
Break GDD features into implementable stories
Ensure stories align with architectural patterns
Create acceptance criteria referencing architecture

Architecture inputs that will be used:

Project structure for file placement
Implementation patterns for code style
Cross-cutting concerns for consistency
System mapping for story assignment

Ready to proceed to epic creation, or any questions about the architecture?"

CRITICAL STEP COMPLETION NOTE

This is the final step. Ensure:

Executive summary is generated
All content is saved to architecture.md
Frontmatter shows all 9 steps completed
User has clear actionable next steps
Handoff to epic workflow is smooth

SYSTEM SUCCESS/FAILURE METRICS

SUCCESS:

Executive summary synthesizes all content
Development setup is complete
Document status updated to 'complete'
Frontmatter shows all steps completed
Workflow status updated (if tracking)
User has clear next steps
Document saved and ready for AI agent consumption

SYSTEM FAILURE:

Missing executive summary
Incomplete development setup
Frontmatter not updated
Status not updated when tracking
No clear next steps provided
User left without actionable guidance

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

Game Architecture Workflow Complete

The Game Architecture workflow transforms a GDD into a comprehensive architecture document through 9 collaborative steps:

Initialize - Validate readiness, discover input documents
Context - Load and understand project requirements
Starter - Select engine and starter templates
Decisions - Make collaborative architectural decisions
Cross-cutting - Define patterns for all systems
Structure - Define project organization
Patterns - Design implementation patterns
Validation - Verify completeness and coherence
Complete - Finalize and provide handoff

This step-file architecture ensures consistent, thorough architecture creation with user collaboration at every step.

On Complete

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete

If the resolved workflow.on_complete is non-empty, follow it as the final terminal instruction before exiting.

step-09-complete.md 10 KB Pysyvä linkki Historia Raaka