SKILL.md
Senior Architect
When to Use
Review or plan system boundaries, dependencies and deployment design for a concrete user task. Gather requirements before recommending technology. This is a manual design workflow; the three bundled Python files are compatibility stubs, not automated analyzers.
Workflow
- Read current repository instructions and actual service interfaces. Record users, key flows, data ownership and measured reliability/latency/capacity needs. Unknown constraints stay unknown.
- Draw the current system from actual endpoints, producers/consumers and storage. Label inferred links and include trust boundaries. Never invent dependencies from filenames alone.
- Compare at least the current/simple option with the proposed change. Explain costs, operational burden, failure domains, data consistency, tenant isolation and migration/rollback behavior.
- Write a small decision record with accepted assumptions, rejected alternatives and a validation plan. Deliver a diagram only when it accurately reflects evidence; architecture formatting does not prove correctness.
- Before implementing, confirm the requested scope; infrastructure provisioning, deployment, data movement and external calls need applicable user authority. Review dependencies before installation and keep credentials out of documents.