Architect Skill Router (companion)

Wrote docs/architecture/routing/skill-route-plan.md. Complete multi-skill route plan and dependency DAG orchestrating 8 specialized Architect skills across 4 execution phases for the Enterprise Event-Driven Payment Migration.

Architect Skill Route Plan: Enterprise Event-Driven Payment Migration [ROUTE-PAY-001]

1. Request Analysis & Intent Classification

The objective is decomposing a legacy monolithic payment processing engine into an asynchronous, event-driven microservices platform. This initiative requires coordination across four distinct technical domains: Backend APIs, Asynchronous Messaging, Cloud Infrastructure & Security, and Reliability Operations.

2. Selected Skills and Execution DAG

The migration plan is structured into four sequential phases forming a strict Directed Acyclic Graph (DAG). Foundation contracts precede transport specifications, which precede infrastructure and reliability operational baselines.

Phase 1: Security & API Contract Foundations
  ├── [threat-modeling-task] ──► Threat Model & Abuse Scenarios
  │                                    │
  └── [rest-api-design] ───────────────┼────────────────────────┐
                                       ▼                        ▼
Phase 2: Authorization & Resilience Mechanics
  ├── [oauth-design] ◄─── (Needs API scopes)                    │
  ├── [idempotency-design] ◄─── (Needs POST refund contracts)  │
  └── [event-driven-architect] ◄─── (Needs payment domain events)
             │
             ▼
Phase 3: Event Relaying & Platform Provisioning
  ├── [outbox-design] ◄─── (Needs topic schemas & Kafka cluster)
  └── [kubernetes-architect] ◄─── (Needs workload resource specs)
             │
             ▼
Phase 4: Reliability Governance & Operations
  └── [sli-slo-design] ◄─── (Needs end-to-end user checkout journey)

3. Boundary & Responsibility Matrix

4. Intake Context and Artifact Lineage

[threat-modeling-task] ──► docs/architecture/security/threat-model.md
                                      │
                                      ▼
[oauth-design] ──────────► docs/architecture/security/oauth-profile.md
                                      │
[rest-api-design] ───────► docs/architecture/api/rest-contract.md
                                      │
                                      ▼
[idempotency-design] ────► docs/architecture/api/idempotency-contract.md
                                      │
[event-driven-architect] ─► docs/architecture/eda/eda-architecture.md
                                      │
                                      ▼
[outbox-design] ─────────► docs/architecture/eda/outbox-contract.md
                                      │
[kubernetes-architect] ──► docs/architecture/k8s/platform-overview.md
                                      │
                                      ▼
[sli-slo-design] ────────► docs/architecture/sre/sli-slo-contract.md

5. Verification & Route Self-Check

No validator was supplied, so no command was run.

Reviewer self-check against routing invariants:

Catalog Verification: PASS. All 8 skill IDs (threat-modeling-task, rest-api-design, oauth-design, idempotency-design, event-driven-architect, outbox-design, kubernetes-architect, sli-slo-design) exist in references/catalog.yml.

• DAG Integrity: PASS. Zero cyclical loops detected; dependencies cascade deterministically across 4 phases.
• Single Ownership: PASS. Every architectural asset has exactly one designated primary skill owner.
• Completeness: PASS. Addresses all five intake concerns stated by Marcus Vance and Sarah Chen.

Next steps

1. Present this Route Plan to Marcus Vance and Sarah Chen for Architecture Review Board endorsement.
2. Initialize Phase 1 execution by loading threat-modeling-task and rest-api-design.
3. Feed resulting threat model boundaries and REST contracts into Phase 2 execution lanes (oauth-design, idempotency-design, and event-driven-architect).