Software Architecture

Design and review software structure with explicit boundaries, dependencies, and tradeoffs. Use when planning new features, refactoring modules, defining service boundaries, or validating architectural decisions before implementation.

nikopj01 Updated

File contents

Software Architecture

Workflow

  1. Capture context and constraints (business goals, non-functional requirements, deadlines).
  2. Define module boundaries and ownership (API, service, repository, data flow).
  3. Evaluate at least two options and document tradeoffs (complexity, cost, risk).
  4. Choose a design and provide a migration plan with rollback points.
  5. List validation checks (tests, metrics, observability, performance budgets).

nikopj01/codex-skills/tree/main/software-architecture commit 957ed59ad0

Frequently asked questions

npx skillmds@latest add nikopj01/software-architecture