Highlights
- Added the
evolutionary-database-designcompanion: a Compatibility pass before architecture and a Transition pass after it for schema, event, API-payload, and file-format changes, with expand/contract staging and an evidence-gated contract step. - Added Integration Discipline to
architecture-guidelines: smart endpoints and dumb pipes, producers consumer-agnostic and consumers transforming, no reach into peer internals, every cross-application edge designed for an untrusted network, asynchronous where the caller can continue, and an architecture-as-code handoff for the peer-internals rule. - Added a quality-characteristics sweep to
requirements-grounding, backed byreferences/quality-model.md(ISO/IEC 25010:2023 with the 2011 rename legend), so unstated non-functional obligations surface as findings with owners instead of manufactured requirements. - Added riskiest-assumption-first sequencing, Assumption Vehicles (proof of concept, prototype, minimum viable product), and parallel-ready slice criteria to
implementation-readiness. - Added delivery-strategy choice to
ci-cd-reliability-architecture(permanent stages, ephemeral stages, production-only progressive exposure) chosen by environment representativeness, with deployment decoupled from release where exposure is progressive and gates restated against the verification stage the strategy provides. - Primers updated; the validator pins the new contract terms and requires the quality-model reference.
Validation
- All skill validators pass (
npm run validate). .agentsand.claudeskill mirrors are identical.- Every changed file is LF in the working tree (
git ls-files --eol).