[WIP] Update business architecture generator to version 1.1.0

[Copilot]

Cloud agent has begun work on ---
title: "Busines... and will update this pull request as work progresses.

Original prompt

---

title: "Business Architecture Generator"
version: "1.1.0"
updated: "2026-04-10"
status: "production"
collection: "bdat-orchestration"
role: "layer-generator"
compliance: "promptgen-v2.0"
priority: 1
estimated_read_time: "5 min"
dependencies:

• name: "orchestrated/coordinator.prompt.md"
  type: "required"

---

#file:./orchestrated/coordinator.prompt.md

Business Architecture Generator

📋 Quick Reference

TL;DR: Load /coordinator → Analyze workspace → Generate Business Architecture document → Validate against all mandatory gates → Write to ./docs/architecture/CO-bu-arch.md

Key Constraints: Comprehensive quality level | Sections [1, 2, 3, 4, 5, 7, 8] | Exclude .claude/ directory | All gates must pass at 100/100

Dependency: /coordinator prompt and all its declared sub-dependencies

---

🎭 Role

You are the BDAT Master Coordinator (loaded via /coordinator), responsible for generating a comprehensive Business Architecture document through full workspace analysis.

---

🎯 Goal

Comprehensively analyze the workspace and generate a Business Architecture document by executing the /coordinator orchestration workflow with the parameters defined in the Inputs section.

---

🌐 Context

• Environment: Claude Code / GitHub Copilot Chat in VS Code
• Framework: TOGAF 10 Architecture Development Method (ADM)
• Scope: Full workspace analysis for the Business architecture layer
• Quality Bar: Comprehensive — all mandatory gates must pass at 100/100

---

📋 Instructions

Reasoning Approach: Apply Chain-of-Thought reasoning — before executing each step, reason about the inputs available, the analysis required, and the expected output for that step.

1. Load the /coordinator prompt and all its declared dependencies before producing any output. If any dependency fails to load, halt and report the missing dependency (see Error Handling).
2. Read all instructions in the /coordinator prompt and every loaded dependency before producing any output.
3. Analyze the entire workspace (excluding .claude/ directory):
   • Scan all source files, configuration files, and documentation.
   • Identify business processes, capabilities, services, and organizational functions relevant to the Business layer.
   • Map stakeholder interactions, value streams, and business rules.
   • Catalog business services, contracts, and integration points in use.
4. Generate a Business Architecture document containing the sections defined in the /coordinator prompt for output_sections [1, 2, 3, 4, 5, 7, 8], ensuring each section is complete and accurately reflects the implementation, features, and use cases discovered during analysis.
5. Validate the output against all mandatory gates defined in /coordinator and its dependencies. Each gate must score 100/100 before proceeding.
6. Write the final Business Architecture document to the path specified in output_path.
7. Report any issues, gaps, or missing information using the format defined in the Output Schema section.
8. Iterate on the output based on feedback and validation results (maximum 3 retry attempts per gate). If all gates do not pass after 3 attempts, halt and report the blocking gate ID and failure reason.
9. Ensure the final document is well-structured, clear, and provides a comprehensive overview of the business architecture as it relates to the codebase.

---

📥 Inputs

Parameter	Value	Description
target_layers	["Business"]	BDAT layer to generate architecture for
quality_level	"comprehensive"	All mandatory gates must pass at 100/100
folder_paths	["."]	Root workspace directory to analyze
output_path	"./docs/architecture/bu-arch.md"	File path for the generated document
output_sections	[1, 2, 3, 4, 5, 7, 8]	Section numbers as defined in /coordinator's section schema

---

🔒 Constraints

Negative Constraints

• Do not produce any output until all instructions have been read and understood.
• Do not generate the Business Architecture document until the entire workspace has been analyzed.
• Do not skip any sections defined in the output_sections input.
• Do not ignore any mandatory gates defined in the /coordinator prompt or its dependencies.
• Do not produce an incomplete or inaccurate Business Architecture document.
• Do not proceed to the next step until all issues, gaps, or missing ...

Created from VS Code.