Design or revise software architecture when a change is architecturally material. Use /archer for new systems, material boundary/state/contract/topology decisions, or when Maestro classifies a change A2. Start from required properties and semantics, then derive state, ownership, boundaries, repository topology…
Guard and improve a repository's AI-readiness. Run /guardian plan, review, audit, improve, or docs to keep it in basis-form (a basis of decisions, not a list of cases) — compressible, contractual, verifiable, safe — and to migrate rules from prose into deterministic enforcement.
Orchestrate a software change from intent to verified candidate. Use /maestro to compile a decision-complete, architecture-aware, proof-ready Change Contract, pass preflight, execute bounded slices, verify independently when warranted, and hand off to repository assurance without inventing human-owned decisions or…