laws-of-software-los
Evaluate substantive software architecture tradeoffs, system boundaries, ADRs, migration strategies, and architectural incident lessons. Use when alternatives, ownership, compatibility, or recovery need an explicit design decision. Do not activate for ordinary implementation, routine bug fixes, generic code review, or formatting without an architectural decision.
Pinned to revision e021ec252689, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/laws-of-software-los/SKILL.md
- skills/laws-of-software-los/LICENSE
- skills/laws-of-software-los/NOTICE.md
- skills/laws-of-software-los/agents/openai.yaml
- skills/laws-of-software-los/assets/adr-template.md
- skills/laws-of-software-los/assets/architecture-review-template.md
- skills/laws-of-software-los/assets/incident-architecture-review-template.md
- skills/laws-of-software-los/assets/migration-plan-template.md
- skills/laws-of-software-los/assets/risk-register-template.md
- skills/laws-of-software-los/assets/system-design-brief-template.md
- skills/laws-of-software-los/references/architecture-playbook.md
- skills/laws-of-software-los/references/decision-frameworks.md
- skills/laws-of-software-los/references/evaluation-guide.md
- skills/laws-of-software-los/references/law-index.md
- skills/laws-of-software-los/references/prompts-and-templates.md
- skills/laws-of-software-los/references/review-rubrics.md
- skills/laws-of-software-los/scripts/adr_lint.py
- skills/laws-of-software-los/scripts/arch_law_check.py
Every link opens the file at its source, pinned to the revision this page describes.