sickn33/agentic-awesome-skills / plugins/aasb-architecture-design/skills/senior-architect
senior-architect
VerifiedPlan and review system architecture using explicit requirements, tradeoffs and evidence; bundled scripts are incomplete stubs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/architecture_patterns.md | markdown | 1.3 KB |
| references/system_design_workflows.md | markdown | 1.1 KB |
| references/tech_decision_guide.md | markdown | 1014 B |
| scripts/architecture_diagram_generator.py | script | 1.9 KB |
| scripts/dependency_analyzer.py | script | 1.9 KB |
| scripts/project_architect.py | script | 1.9 KB |
references/system_design_workflows.md
View on GitHub# System design workflow
1. Capture the user problem, success metric, observed workload and hard constraints. Record assumptions and missing evidence.
2. Trace one real request/event from caller through authorization, state change and external effects; list data owners and failures.
3. Describe the current design and the smallest change, then compare an alternative on reliability, consistency, latency, cost and team ownership.
4. Specify interfaces, idempotency/ordering, timeout/cancel, tenant boundaries, secrets and rollback. Schema evolution must support mixed-version deploys where relevant.
5. Draft a migration with checkpoints, safe abort conditions and observable correctness, including data reconciliation and rollback limits.
6. Propose bounded validation against realistic isolated fixtures. Record actual results separately from forecasts; do not run production load or provision resources without authority.
Deliver: evidence-linked current diagram, proposed diagram, decision record, unresolved risks, validation and rollout plan. No bundled script automates these steps.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |