Menu
DEPRECATED — consolidated into bmad-architecture create intent - this skill will be removed in v7 in favor of `bmad-architecture`.
| name | bmad-create-architecture |
| description | DEPRECATED — consolidated into bmad-architecture create intent - this skill will be removed in v7 in favor of `bmad-architecture`. |
This skill was consolidated into bmad-architecture. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-create-architecture.toml override files keep working. New work should invoke bmad-architecture directly — it detects create / update / validate intent from the conversation.
Resolve customization: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-create-architecture.toml and bmad-create-architecture.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).
Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.
Emit a deprecation notice to the user in {communication_language}:
Notice:
bmad-create-architectureis deprecated and will be removed in a future release. It now forwards tobmad-architecturewith create intent. To silence this notice and access the full new customization surface (spine_template,spine_output_path,run_folder_pattern,doc_standards,external_sources,external_handoffs,finalize_reviewers), migrate_bmad/custom/bmad-create-architecture.tomlto_bmad/custom/bmad-architecture.tomland invokebmad-architecturedirectly next time. Customization fields that were in this version still remain in the new version and will be respected if present in_bmad/custom/bmad-architecture.toml, but the new version also supports additional fields that you can take advantage of by migrating.
Invoke bmad-architecture with the following context. Pass these as the activating context so bmad-architecture honors them instead of resolving its own customization from scratch:
create — skip bmad-architecture's usual intent detection step.bmad-architecture's own customize.toml for the four legacy fields. For everything else (spine_template, spine_output_path, run_folder_pattern, doc_standards, external_sources, external_handoffs, finalize_reviewers), use bmad-architecture's own defaults and overrides as normal:
activation_steps_prepend = the resolved value from step 1activation_steps_append = the resolved value from step 1persistent_facts = the resolved value from step 1on_complete = the resolved value from step 1bmad-architecture takes the workflow from here. Do not execute any further steps in this shim.
Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".
Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec".
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"