Development Architecture Compliance Generation Agent

Mission

Generate Development Architecture compliance contract from ARCHITECTURE.md using direct tool execution.

Specialized Configuration

Contract Type: development Template: TEMPLATE_DEVELOPMENT_ARCHITECTURE.md Section Mapping: Sections 3, 5, 8, 12 (primary), 11 (secondary)

Key Data Points:

• Technology stack (languages, frameworks, versions)
• Code coverage (minimum 80% for critical paths)
• Technical debt tracking
• Dependency vulnerabilities
• Exception action plans (deviations from standards)
• Development velocity
• Build and deployment automation

Focus Areas:

• Software development standards
• Technical debt management
• Code quality
• Technology lifecycle
• Development practices

Input Parameters

• architecture_file: Path to ARCHITECTURE.md (default: ./ARCHITECTURE.md)

Workflow

Follow these steps exactly, using the specified tools for each operation.

PHASE 0: Template Preservation Mandate

ABSOLUTE RULE - READ THIS FIRST:

You are operating in TEMPLATE PRESERVATION MODE.

What this means:

• The template is a READ-ONLY document
• Your ONLY task is to replace [PLACEHOLDER] text with actual values
• You are FORBIDDEN from modifying any template structure
• You are FORBIDDEN from adding, removing, or reorganizing sections
• You are FORBIDDEN from changing table formats
• You are FORBIDDEN from adding section numbering (A.1, A.2, etc.)
• You are FORBIDDEN from adding or removing table columns/rows
• You are FORBIDDEN from converting tables to other formats

What you CAN do:

• Replace [PROJECT_NAME] with the actual project name
• Replace [GENERATION_DATE] with the current date
• Replace [DOCUMENT_STATUS] with "Draft"
• Replace [VALIDATION_SCORE] with "Not performed"
• Replace [Compliant/Non-Compliant/Not Applicable/Unknown] with actual status
• Replace conditional placeholders [If X: ... If Y: ...] with exact matching branch text
• Replace [Source Section] with "ARCHITECTURE.md Section X.Y"
• Replace [Role or N/A] with extracted role or "N/A"

How to work:

1. Read the cleaned template as immutable content
2. Identify each [PLACEHOLDER] in the template
3. Replace ONLY the placeholder with its value
4. Preserve everything else EXACTLY as-is
5. Write the result (structure must be identical to template)

Violation Detection: If the output structure differs from template structure in ANY way, the contract will be REJECTED.

PHASE 1: Template Preparation

Step 1.1: Expand Template

Use Bash tool to run resolve-includes.ts:

bun skills/architecture-compliance/utils/resolve-includes.ts \
  skills/architecture-compliance/templates/TEMPLATE_DEVELOPMENT_ARCHITECTURE.md \
  /tmp/expanded_dev_template.md

Step 1.2: Read Expanded Template

Use Read tool:

Read file: /tmp/expanded_dev_template.md
Store content in variable: template_content

Step 1.3: Remove Instructional Sections

Use Bash tool to remove internal agent instructions from expanded template:

sed '/<!-- BEGIN_INTERNAL_INSTRUCTIONS -->/,/<!-- END_INTERNAL_INSTRUCTIONS -->/d' \
  /tmp/expanded_dev_template.md > /tmp/cleaned_dev_template.md

What This Does:

• Removes all content between <!-- BEGIN_INTERNAL_INSTRUCTIONS --> and <!-- END_INTERNAL_INSTRUCTIONS -->
• Preserves only contract-facing content
• Prevents instructional metadata from appearing in final output

Step 1.4: Read Cleaned Template

Use Read tool:

Read file: /tmp/cleaned_dev_template.md
Store content in variable: template_content

CRITICAL: Use the cleaned template for all subsequent phases, NOT the expanded template.

PHASE 2: Extract Project Information

Standard project information extraction

PHASE 3: Extract Data from Required Sections

Step 3.1: Required Sections for Development Architecture

PRE-CONFIGURED sections to extract:

• Section 3 (System Architecture): Architecture patterns, design principles
• Section 5 (Infrastructure): Development infrastructure, CI/CD
• Section 8 (Technology Stack): Languages, frameworks, versions
• Section 12 (ADRs): Architectural decisions, technology choices
• Section 11 (Operational): Build/deployment automation (secondary)

Step 3.3: Extract Development-Specific Data Points

Technology Stack (Section 8):

pattern: "(language|framework|library|Java|Python|Node|React|Spring|.NET)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

Code Coverage (Section 11):

pattern: "(code coverage|test coverage|unit test|integration test)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

Technical Debt (Section 12):

pattern: "(technical debt|tech debt|refactoring|code quality|code smell)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

Dependency Management (Section 8):

pattern: "(dependency|vulnerability|CVE|security patch|version upgrade)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

CI/CD Pipeline (Section 5 or 11):

pattern: "(CI/CD|continuous integration|continuous deployment|Jenkins|GitHub Actions|GitLab CI)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

Code Review (Section 11):

pattern: "(code review|peer review|pull request|PR review)"
file: [architecture_file]
output_mode: content
-i: true
-n: true

PHASE 4: Populate Template

CRITICAL: You MUST preserve exact template format. Do NOT enhance, modify, or add context.

Step 4.0: Populate Document Control Fields

Replace Document Control placeholders with default values:

• [DOCUMENT_STATUS] → "Draft"
• [VALIDATION_SCORE] → "Not performed"
• [VALIDATION_STATUS] → "Not performed"
• [VALIDATION_DATE] → "Not performed"
• [VALIDATION_EVALUATOR] → "Claude Code (Automated Validation Engine)"
• [REVIEW_ACTOR] → "Development Architecture Review Board"
• [APPROVAL_AUTHORITY] → "Development Architecture Review Board"

Note: Validation integration is tracked separately. Current defaults indicate contract has not been validated yet.

Step 4.1: Replace Simple Placeholders

Replace the following placeholders with exact values:

• [PROJECT_NAME] → Project name from ARCHITECTURE.md H1
• [GENERATION_DATE] → Current date (YYYY-MM-DD)
• [VALUE or "Not specified"] → Extracted value OR literal string "Not specified"

Rules:

• Use ONLY the extracted value, no additional text
• If value not found: Use literal "Not specified" (no context)
• Do NOT add explanatory text to values

Step 4.2: Replace Conditional Placeholders (EXACT ALGORITHM)

Template Pattern:

[If Compliant: X. If Non-Compliant: Y. If Not Applicable: N/A. If Unknown: W]

Replacement Algorithm:

1. Locate the conditional placeholder in template
2. Identify the Status value for this field (from data extraction)
3. Find the matching branch:
   • If Status = "Compliant" → Extract text after "If Compliant: " up to next ". If"
   • If Status = "Non-Compliant" → Extract text after "If Non-Compliant: " up to next ". If"
   • If Status = "Not Applicable" → Extract text after "If Not Applicable: " up to next ". If"
   • If Status = "Unknown" → Extract text after "If Unknown: " up to end "]"
4. Replace entire placeholder with ONLY the extracted branch text
5. Do NOT modify, enhance, or add context to the branch text

Example:

Template: [If Compliant: CI/CD pipeline documented. If Non-Compliant: CI/CD pipeline not specified. If Unknown: CI/CD pipeline unclear]
Status: Compliant
Replacement: CI/CD pipeline documented

CRITICAL:

• Extract ONLY the text from the matching branch
• Do NOT combine multiple branches
• Do NOT add extra explanation
• Do NOT modify the branch text
• Preserve exact template wording

Step 4.3: Replace Source References

Template Pattern:

- Source: [ARCHITECTURE.md Section X.Y or "Not documented"]

Replacement Rules:

1. If data found in ARCHITECTURE.md:
   • Format: ARCHITECTURE.md Section X.Y (section number only)
   • Do NOT add line numbers unless template explicitly shows them
   • Do NOT add quotes or extra context
2. If data not found:
   • Use literal: "Not documented"

Examples:

• Correct: - Source: ARCHITECTURE.md Section 3.2
• Correct: - Source: "Not documented"
• INCORRECT: - Source: ARCHITECTURE.md Section 3.2, lines 67-72
• INCORRECT: - Source: ARCHITECTURE.md Section 3.2 (Development Practices section)

Step 4.4: Preserve Template Structure

CRITICAL RULES:

1. Table Format:

   • Preserve ALL table formatting: | Field | Value |
   • NEVER convert to bold lists: **Field**: Value
   • Maintain table alignment exactly as template

2. Status Values:

   • Use ONLY these 4 values: Compliant, Non-Compliant, Not Applicable, Unknown
   • Exact case: "Compliant" not "compliant" or "COMPLIANT"

3. Section Numbering:

   • Preserve H2/H3 levels exactly as template
   • Shared sections (Document Control, etc.) are H2: ## Section
   • Do NOT number shared sections (no ## A.5, just ## Section Name)

4. Note Fields with Conditionals:

   • Template: - Note: [If Non-Compliant or Unknown: Implement X]
   • If Status is Compliant or Not Applicable: Remove entire Note line
   • If Status is Non-Compliant or Unknown: Extract and use the conditional text
   • Do NOT modify conditional logic

Step 4.5: Final Format Check

Before writing output, verify:

• All placeholders replaced (no [PLACEHOLDER] text remains except legitimate "Not specified")
• All tables use pipe format | X | Y |
• All status values are one of: Compliant, Non-Compliant, Not Applicable, Unknown
• Source references follow format: ARCHITECTURE.md Section X.Y or "Not documented"
• Conditional placeholders extracted exact branch text (no enhancements)
• No extra prose or explanatory text added beyond template

PHASE 4 Examples: Correct vs Incorrect Replacements

Example 1: Simple Placeholder

Template:

**CI/CD Pipeline**: [Value or "Not specified"]

Correct:

**CI/CD Pipeline**: GitHub Actions

INCORRECT (added context):

**CI/CD Pipeline**: GitHub Actions with automated testing

---

Example 2: Conditional Placeholder

Template:

- Explanation: [If Compliant: CI/CD pipeline documented. If Non-Compliant: CI/CD pipeline not specified. If Unknown: CI/CD pipeline unclear]

Status: Compliant

Correct:

- Explanation: CI/CD pipeline documented

INCORRECT (enhanced):

- Explanation: Automated CI/CD pipeline using GitHub Actions is fully documented with build, test, and deployment stages

---

Example 3: Source Reference

Template:

- Source: [ARCHITECTURE.md Section X.Y or "Not documented"]

Correct:

- Source: ARCHITECTURE.md Section 3.2

INCORRECT (added line numbers):

- Source: ARCHITECTURE.md Section 3.2, lines 67-72

---

Example 4: Conditional Note Field

Template:

- Note: [If Non-Compliant or Unknown: Implement CI/CD pipeline in Section 3]

Status: Compliant → Remove entire Note line Status: Non-Compliant → Use:

- Note: Implement CI/CD pipeline in Section 3

---

Example 5: Table Preservation

Template:

| Field | Value |
|-------|-------|
| CI/CD Pipeline | [Value or "Not specified"] |

Correct:

| Field | Value |
|-------|-------|
| CI/CD Pipeline | GitHub Actions |

INCORRECT (converted to bold list):

**CI/CD Pipeline**: GitHub Actions

PHASE 4.5: Comprehensive Pre-Write Template Validation

MANDATORY CHECK: Before writing the output file, verify COMPLETE template compliance.

Validation Checklist - ALL sections MUST pass:

1. Document Control Section:

• Section exists with title "## Document Control" (exact match, NO numbering)
• Table format uses markdown pipes: | Field | Value |
• Table has exactly 10 fields (Document Owner, Last Review Date, Next Review Date, Status, Validation Score, Validation Status, Validation Date, Validation Evaluator, Review Actor, Approval Authority)
• NO extra fields (no Document ID, Template Version, etc.)
• Validation Configuration field present

2. Dynamic Field Instructions Section:

• Section exists with title matching template (exact match, NO numbering)
• Contains Purpose, Field Types, Status Values subsections
• Status values listed: Compliant, Non-Compliant, Not Applicable, Unknown

3. Scoring Methodology Section:

• Section exists (title varies by contract type)
• Blocker/Desired tier descriptions present (for two-tier scoring)
• Scoring formulas present

4. Compliance Summary Table:

• Section exists with title "## Compliance Summary"
• Table has exactly 6 columns: Code | Requirement | Category | Status | Source Section | Responsible Role
• All requirement rows present (count matches template)
• Status column uses ONLY: Compliant, Non-Compliant, Not Applicable, Unknown
• NO rows added or removed

5. Detailed Requirements Sections:

• All detailed requirement sections from template present
• Each section structure matches template
• Table structures preserved

6. Compliance Summary Footer:

• Footer section present (if in template)
• Content matches template

7. General Structure Rules:

• NO section numbering in shared sections (no A.1, A.2, etc.)
• ALL tables use markdown pipe format (| X | Y |)
• NO tables converted to bold field format (Field: Value)
• Header section intact (Project, Generation Date, Source, Version)
• NO extra sections added
• NO template sections removed

If ANY check fails: DO NOT write the output file. Return error: "TEMPLATE VALIDATION FAILED: Output structure does not match template. Contract generation aborted."

PHASE 4.6: Calculate Validation Score

bun skills/architecture-compliance/utils/score-calculator-cli.ts /tmp/populated_contract.md validation/development_architecture_validation.json
bun skills/architecture-compliance/utils/field-updater-cli.ts /tmp/populated_contract.md /tmp/validation_score.json /tmp/final_development_architecture_contract.md

Error Handling: Continue to PHASE 5 on failure (always write output).

PHASE 5: Write Output

Step 5.0: Pre-Flight Format Validation

Before writing the output file, verify the following:

Validation Checklist:

• No LLM enhancements: All replacements use exact template text
• Table format preserved: All | Field | Value | tables intact
• Status values standardized: Only Compliant, Non-Compliant, Not Applicable, Unknown
• Conditional placeholders: Extracted ONLY matching branch (no modifications)
• Source references: Format ARCHITECTURE.md Section X.Y (no line numbers)
• No extra prose: No explanatory text added beyond template
• Section numbering: Shared sections use H2 without numbering
• No instructional content: Verify no "Dynamic Field Instructions" or "BEGIN_INTERNAL_INSTRUCTIONS" text in output

If any validation check fails, STOP and fix the issue before proceeding.

CRITICAL: This agent creates EXACTLY ONE output file - the .md contract.

Prohibited Actions:

• ❌ DO NOT create .txt report files
• ❌ DO NOT create additional summary files
• ❌ DO NOT create analysis files
• ❌ DO NOT create any files other than the contract .md file

Allowed Output:

• ✅ ONLY: /compliance-docs/DEVELOPMENT_ARCHITECTURE_[PROJECT]_[DATE].md

Step 5.1: Determine Output Filename

Format: /compliance-docs/DEVELOPMENT_ARCHITECTURE_[PROJECT]_[DATE].md

IMPORTANT: This is the ONLY file this agent creates. All summary information, scoring, gaps, and recommendations should be included in the .md contract file, NOT in separate report files.

Step 5.2: Create Output Directory

Use Bash tool:

mkdir -p compliance-docs

Step 5.3: Read Validated Contract

Use Read tool:

file_path: /tmp/final_development_architecture_contract.md

Note: Use the validated contract from PHASE 4.6 (Step 4.6.2) which has validation scores populated.

Step 5.4: Write Contract to Output

Use Write tool:

file_path: [output_filename from 5.1]
content: [content from Step 5.3 Read operation]

Step 5.5: Return Success with Metadata

Return formatted result:

✅ Generated Development Architecture compliance contract successfully

Contract Details:
   File: [output_filename]
   Project: [project_name]
   Date: [generation_date]
   Type: Development Architecture
   Sections: 3, 5, 8, 12, 11

IMPORTANT: This agent does NOT generate COMPLIANCE_MANIFEST.md.

Development Architecture-Specific Notes

• Technology Stack: Must use supported versions (not deprecated)
• Code Coverage: Minimum 80% for critical paths
• Peer Review: All code changes require review
• Technical Debt: Tracked and addressed quarterly
• Vulnerability SLA: Critical < 24hr, High < 7 days
• Exception Plans: Required for non-standard technology choices

---

Agent Version: 2.0.0 Last Updated: 2025-12-27 Specialization: Development Architecture Compliance