Production-first: decisions grounded in evidence
A choice that is expensive to reverse, or that everything else builds on, gets evidence before code; ordinary local choices get the existing pattern.
Workflow
- State the decision, the constraint it must meet (scale, latency, licence, platform, team, budget) and the evidence that would settle it.
- Read the existing implementation, constraints and recorded decisions first; if they settle it, reuse the pattern — no research for a local definition or a known stdlib operation.
- Gather evidence for what the project cannot answer (below), cross-checking what is hard to reverse or contested; choose by fit, correctness, maintenance and measured constraints, since adoption is not proof it fits here.
- Probe the remaining risk, then record the decision where the project keeps such records — an ADR only if it uses them.
Acceptable evidence
Closest to actual behavior first:
- Official docs and changelog for the exact version in use: migration notes, deprecations, support windows, licence terms.
- Source code or the shipped artifact when docs and behavior disagree.
- Maintenance signals: recent releases, issue-tracker response, open advisories, a support policy. "Popular in a blog post" is not one; years untouched with a long open-issue backlog is counter-evidence.
- Issue trackers for known failure modes and version-specific bugs; read the resolution, not the title.
- Reproducible benchmarks on a comparable workload with method and hardware stated; vendor benchmarks only start the search.
- Our own probe: the smallest test that exercises the uncertain behavior in this stack.
Say which you used and what stayed unverified; a claim with no evidence class is a guess.
Test before integration
For an unfamiliar dependency or mechanism, probe first in a task-sized sandbox: one real call path, the edge case you doubt, the upgrade or the failure mode; benchmark only when performance drives the choice. Installation, paid calls and outward actions need authorization per OPS §1.
Research depth
Stop once resolved: a narrow fact needs its owning source; a consequential choice needs alternatives, counterevidence and a probe of what remains. Ship the tradeoffs and remaining uncertainty with the decision.
1---2name: production-first-decisions3description: 'Use before committing to a consequential tool, library, standard or production mechanism: "should we use X", "which library", "is X maintained", auth/crypto/queue/database choices, or replacing a working one. Check project constraints first, then primary-source evidence (docs, changelogs, maintenance signals, issue trackers, benchmarks, own probe) before integration. Not for module structure (architecture-simplicity) or minimalism-only requests (ponytail); ordinary implementation needs no skill.'4license: MIT5compatibility: any project6metadata:7 source: https://skillmd.com/skills/oleg494/production-first-decisions8 version: "6.1.0"9---1011# Production-first: decisions grounded in evidence1213A choice that is expensive to reverse, or that everything else builds on, gets evidence before code; ordinary local choices get the existing pattern.1415## Workflow16171. State the decision, the constraint it must meet (scale, latency, licence, platform, team, budget) and the evidence that would settle it.182. Read the existing implementation, constraints and recorded decisions first; if they settle it, reuse the pattern — no research for a local definition or a known stdlib operation.193. Gather evidence for what the project cannot answer (below), cross-checking what is hard to reverse or contested; choose by fit, correctness, maintenance and measured constraints, since adoption is not proof it fits here.204. Probe the remaining risk, then record the decision where the project keeps such records — an ADR only if it uses them.2122## Acceptable evidence2324Closest to actual behavior first:2526- **Official docs and changelog** for the exact version in use: migration notes, deprecations, support windows, licence terms.27- **Source code or the shipped artifact** when docs and behavior disagree.28- **Maintenance signals:** recent releases, issue-tracker response, open advisories, a support policy. "Popular in a blog post" is not one; years untouched with a long open-issue backlog is counter-evidence.29- **Issue trackers** for known failure modes and version-specific bugs; read the resolution, not the title.30- **Reproducible benchmarks** on a comparable workload with method and hardware stated; vendor benchmarks only start the search.31- **Our own probe:** the smallest test that exercises the uncertain behavior in this stack.3233Say which you used and what stayed unverified; a claim with no evidence class is a guess.3435## Test before integration3637For an unfamiliar dependency or mechanism, probe first in a task-sized sandbox: one real call path, the edge case you doubt, the upgrade or the failure mode; benchmark only when performance drives the choice. Installation, paid calls and outward actions need authorization per OPS §1.3839## Research depth4041Stop once resolved: a narrow fact needs its owning source; a consequential choice needs alternatives, counterevidence and a probe of what remains. Ship the tradeoffs and remaining uncertainty with the decision.