software-architecture
Installation
SKILL.md
Software Architecture
Use this skill to turn an intended outcome into a design that is understandable, testable, operable, secure, and changeable. Architecture is a set of consequential decisions and constraints, not a mandatory folder layout or a collection of patterns.
Scale the work
Use this skill when building or evolving security tooling and its supporting software. Select depth by risk and affected boundaries, not codebase size alone.
| Task | Minimum useful work |
|---|---|
| Local fix or simplification | Identify the behavior to preserve, inspect the affected seam, make the change, and run focused verification. Skip topology comparisons and design documents unless a boundary changes. |
| New tool, library, or cohesive application | Capture outcomes and constraints, name responsibilities and public contracts, identify state and side effects, then prove the riskiest path. One file is sufficient when responsibilities remain clear and local. |
| Cross-module change, service, or larger system | Add relevant quality scenarios, dependency/data ownership, failure and migration design, operational checks, and consequential decision records. |
The workflow below supplies decisions to make, not mandatory documents for every task. Keep a small design in the task notes; use the repository's design records when decisions need to persist.