analyze-architecture

Map a Jira requirement to an architecture graph by cross-referencing functional, code, and architecture layers to surface affected components. This structured approach assesses traceability and impact, generating a write-back report for the Jira ticket.

The 8-layer model is an architecture graph framework used to analyze requirements and derive impact, anchors, and alignment. It enables consistent requirement placement by cross-referencing functional scenarios with the code graph to identify dependencies and reuse opportunities.

Yes, you can analyze ad-hoc plain-text requirements without a direct Jira link. Providing a plain-text requirement triggers the same analysis workflow, mapping the text against the architecture graph to surface affected nodes and generate structured guidance.

Trace functional scenarios to backend code components by cross-referencing the architecture graph with the code graph. This anchors user-facing elements and backend dependencies to functional scenarios, enabling complete traceability from requirement to delivery.

Requirement impact analysis does not automatically update the architecture graph. It generates a structured analysis report that can be appended to a Jira ticket and is optionally committed to the architecture graph only after explicit user confirmation.

Generate an architecture impact report for a Jira epic by providing the Jira URL to trigger the analysis workflow. The system derives impact, anchors, and write-back guidance across the 8-layer model, producing a structured report documenting findings and recommended actions.