adr-management
When you need to record why a decision was made — creates and manages Architecture Decision Records.
13 skills tagged design · lifecycle axis.
When you need to record why a decision was made — creates and manages Architecture Decision Records.
When frontend and backend need to agree before coding — designs REST/gRPC APIs with OpenAPI spec.
When data modeling decisions will outlast the code — schema design, normalization, migration planning, indexing.
When future-you needs to know why past-you chose this — ADR authoring with context, decision, consequences.
When you're not sure what depends on what — builds dependency graphs, detects cycles, audits for staleness and CVEs.
When "how long will this take?" needs a real answer — PERT estimation, relative sizing, confidence intervals.
Pre-compute once, share via context object to all pipeline stages.
Before you ship something that keeps you up at night — identifies risks, scores probability/impact, plans mitigations.
Single schema powers defaults, validation, storage, and UI generation.
Composable evaluation — independent micro-scorers with shared context and explicit weights.
When you need to see the big picture before building — component diagrams, data flow, trade-off analysis.
When a task feels too big to start — breaks it into dependency-ordered subtasks with T-shirt sizing.
Before attackers find the holes — identifies STRIDE threats, assesses risk, plans mitigations.