game-architect

You can generate structured design documents by running a phase-driven pipeline that formalizes game architecture requirements into requirement.md, technical_design.md, and implementation.md artifacts within an architect/ directory for new game projects.

The standard pipeline for game architecture requirements analysis is a phase-driven workflow progressing from Phase 1 requirement drafting, to Phase 2 technical design creation, and Phase 3 implementation plan finalization, exporting structured artifacts into an architect/ directory.

You structure an implementation plan for a major game feature by finalizing it during Phase 3 of the architecture pipeline, ensuring clear separation of concerns, modularity, and future evolution points within the exported implementation.md document.

Yes, you can use this pipeline to document requirements for major game features, as its applicability explicitly covers generating requirement analysis, technical design, and implementation plans for both new game projects and major features.

The Phase 0 review workflow is a required preliminary step in the game architecture pipeline that ensures proper review and references to standard design documents before generating the formal phase-driven outputs.

A limitation of using automated pipelines for game design documentation is that while it standardizes project kickoffs and handoffs, it focuses on formalizing existing requirements and does not replace the initial ideation or creative game design process needed before Phase 1.