jssi-architecture-review

Run the full JSSI architecture-review pipeline on an app repo and produce the architecture-vault packet (diagrams + findings + brief) for a board review. Pass the app repo path as arguments.

Use when an architect or CI pipeline has dependency-boundary and user-flow JSON maps and needs Mermaid diagram output — a layered architecture flowchart, a swim-lane sequenceDiagram per journey, and a drill-down flowchart per journey with NO-GO overlays. Trigger phrases include "generate architecture diagrams", "diagram these maps", "produce Mermaid from the boundary map", or "visualize the user flows". Accepts both maps inline. Emits ONLY Mermaid fenced code blocks — zero prose anywhere in output.

Use when an architect, tech lead, or CI pipeline has completed the five JSSI mapper passes (dependency-boundary, user-flow, resilience, performance, contract-inventory) plus a risk profile and standards config and needs a machine-readable findings report — suitable trigger phrases include "run the architecture findings engine", "produce a findings report from these maps", "check the maps against our standards", or "do a pre-JAD findings pass". Accepts all mapper JSON outputs plus risk-profile and standards inline in the prompt. Emits exactly one fenced JSON block with NO-GO/BLOCKING findings (machine-verifiable, grounded evidence required) and ADVISORY/QUESTION findings (board_call=true). Does NOT write code, suggest fixes, run tools, or render an overall verdict.

Use when a developer, tech lead, or CI pipeline needs to execute the full architecture review pipeline from repo path to vault packet — trigger phrases include "run arch-review", "orchestrate the architecture review", "arch-review on an app repo path", or "sequence the architecture mappers and engines". Runs risk-classify first, fans out all five mappers in parallel (dependency-boundary-mapper, user-flow-mapper, resilience-mapper, performance-mapper, contract-inventory-mapper), then drives arch-diagram-engine and arch-findings-engine after mapper outputs land, then calls arch-vault-assembler last. Fail-closed on empty or missing repo path — no sub-skills dispatched. Degraded-not-silent when a mapper errors — pipeline continues and annotates the degraded note. Cap-logged when flow count exceeds drill cap. Emits ONE fenced JSON ORCHESTRATION TRACE, no prose anywhere.

Use when arch-findings-engine has produced a findings object, arch-diagram-engine has produced a Mermaid diagram set, and a risk profile plus conformance summary are available — to assemble the complete architecture-vault packet for a JSSI board review. Trigger phrases include "assemble the vault packet", "produce the 00-brief", "build the architecture review brief", or "package the findings for the board". Accepts all inputs inline. Emits 00-brief.md (seven fixed sections in mandatory order) followed by a fenced manifest block listing every packet file. Never renders an overall verdict — the board owns the thumbs-up.