SKILL.md · 48000
Testability Milestone per component and never require a component's automated test gate before that component crosses its own testability line.
- Name the CI Milestone, hand enforcement to a human. State which phase stands up CI (the first lit phase), and make explicit that turning CI into an enforced required check / branch-protection rule is a manual platform step the agent cannot do — surface it as a user action item, not a done task.
- Net the seams, not the corpse. Anchor safety at externally observable contracts (protocols, schemas, wire/file formats, endpoints) with a ranked oracle (running instance → recorded I/O → code-as-spec → self-frozen golden master when no external reference exists or is permitted). Don't sink sprints resurrecting a dead toolchain just to run a test that gets deleted at rewrite.
- Keep it generic. Express commands and gates in terms of the project's package manager / test runner / CI — never assume a specific stack.
- Red-team every phase before implementing (H1–H8). Walk each phase plan
against
references/migration-hazards.mdand fold the fixes into tasks/exit criteria first — a hazard caught in planning is a task; in review, rework; in prod, an incident. These tactical hazards (incomplete quarantine, framework codemods, runtime/base-image lockstep, route-class enumeration, data-store upgrade paths, transitional-insecure-state noise, stacked-PR/trunk drift, living-doc drift) are what strategic scaffolding alone keeps missing.