axisrobo

arch-design

Design a new technical architecture from requirements. Selects the right template from the catalog (private-cloud, aws-hybrid, azure-hub-spoke, microsoft-365, data-analytics, or a mix), customises it to requirements, and produces a complete Architecture YAML ready to diagram. Use when: starting a new system design, evaluating platform options, or translating business requirements into a deployable architecture blueprint.

arch-diagram

Generate a draw.io architecture diagram (or PNG) from an Architecture YAML file. Produces .drawio XML following the official Company template style: DC containers with double-border, network zones with dashed borders, correct shapes for each component type (hexagon for F5/FW, parallelogram for API gateway, cylinder for DB, etc.), edges labeled with protocol and auth. Optionally exports PNG. Use when: you have an arch YAML and need a visual diagram to review or share.

arch-enforce

CI enforcement gate. Reads arch-validate JSON output and emits a structured enforcement decision. Use in CI pipeline only, not for human review. Inputs: validate_result.json and arch-gate-policy.yaml. Outputs: enforce_result.json with exit_code for pipeline consumption.

arch-optimize

Generate a prioritized improvement plan for an architecture. Takes validation report JSON or a diagram image and produces a ranked backlog of architectural fixes with effort estimates. Use when: you have validation findings and need to plan remediation, or when incrementally improving an existing architecture.

arch-report

Generate documentation from an architecture diagram or validation report. Produces Confluence-ready pages, executive summaries, or risk briefs. Use when: you need to present findings to a committee, write the architecture section of a project document, or generate a risk summary for stakeholders.

API & Backend Listed

arch-req-from-api

Fetch application metadata from CMDB (ServiceNow, etc.) or Enterprise Architecture systems via REST API or CSV export. Provides high-confidence physical location and ownership data. Does NOT provide tech stack, protocols, or auth — those must come from other readers or interview. Use before arch-req-merge.

arch-req-from-diagram

Extract architecture requirements from diagram files or images. Supports: draw.io XML (.drawio), D2 (.d2), Architecture YAML (.yaml), and architecture images (.png/.jpg) via Claude Vision API. Outputs a partial requirements YAML with confidence scores. Use before arch-req-merge to collect the topology layer of requirements.

arch-req-from-doc

Extract architecture requirements from documents (PDF, DOCX, MD, TXT). Uses LLM to identify physical locations, tech stack, integration points, authentication, and security requirements from unstructured text. Outputs a partial requirements YAML. Medium confidence — always verify. Use before arch-req-merge to collect the business context layer.

Code & Development Listed

arch-req-merge

Merge multiple partial requirements YAML files from different readers into one consolidated req.yaml. Detects field conflicts between sources, identifies critical gaps, and produces a gap report. Run after all readers, before the gap-filling interview in arch-requirements.

arch-requirements

Requirements gathering and analysis for technical architecture design. Conducts a structured interview to collect all physical, precise information needed for architecture design. Outputs a Requirements Document (REQ.md + req.yaml) that becomes the direct input to arch-design. Use BEFORE arch-design. Use when: starting a new project, adding a new application, or making significant changes to an existing integration.

Code & Development Listed

arch-review

Architecture committee review. Evaluates a diagram or design document against enterprise standards with structured scoring per dimension. Produces a gate decision: APPROVED / APPROVED WITH CONDITIONS / REJECTED. Use when: preparing for architecture review board, requesting committee sign-off, or doing a pre-commit standards check before diagram is submitted.

arch-security

Deep-dive security audit of a technical architecture diagram. Focused exclusively on authentication, authorization, credential protection, network boundaries, and data classification. Does NOT score overall quality — produces a prioritized security finding list. Use after arch-validate when you want a security specialist's deep cut.

arch-validate

Validate a technical architecture diagram image against enterprise architecture standards. Scores six dimensions (10 pts total), outputs structured JSON + text report. Use when: reviewing a draw.io export, checking a new design before committee review, or running CI validation on a committed diagram.

arch-workflow

Pipeline gatekeeper that enforces the mandatory ArchHarness stage order (requirements -> design -> draw -> validate -> enforce -> security/review -> optimize -> report). Checks required artifacts and gate decisions before allowing the next stage; refuses to skip ahead or fabricate predecessor outputs. Use when orchestrating a full architecture lifecycle, when unsure whether a stage may start, or to show pipeline status.