{"id":24103,"plugin_id":"plugins_6ab39a6b4b408191b4220e44e482f464","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:57.152Z","digest":"a20816d12ca06c2b06069312da7b4cde43004e1245d3eba81c2c0ddc1e6c49d3","against":null,"payload":{"name":"architecture-router","description":"Route architecture work from discovery through design, review, and decision records.","included_files":[],"skill_md_contents":"---\nname: architecture-router\ndescription: Route architecture work from discovery through design, review, and decision records.\n---\n\n# Architecture Router\n\nUse for software architecture, system design, or technical strategy requests.\n\n1. Classify the task: requirements discovery, options/trade-offs, system description, quality review, or decision record.\n2. Gather the relevant scale, workload, user and data boundaries, constraints, existing systems, team/operational capacity, and time horizon. Ask focused questions only where missing facts change the decision; otherwise label assumptions.\n3. Route to `requirements-and-quality`, `system-design`, `architecture-decisions`, or `architecture-review`; combine narrowly as needed.\n4. Keep cloud/provider recommendations proportional to stated constraints. Compare viable alternatives rather than defaulting to fashionable technology.\n5. State evidence, assumptions, risks, confidence, and next validation steps.\n\nDeliver advisory artifacts. Never imply that a conceptual architecture has been implemented, load-tested, secured, or certified.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}