aibdd-principle-starter-stableness

What problem does it solve?

This Skill prevents teams from discovering missing test and runtime foundations only after starting Red/Green/Refactor execution, which causes wasted work, flakiness, and hidden wiring rot.

Core Features & Use Cases

• Phase-starter stability guarantees: Ensures the minimum runnable foundations exist before each execution phase, so work happens on the actual feature boundary instead of environment patching.
• Deterministic scenario isolation: Requires repeated runs of the same acceptance scenarios to produce stable outcomes without state leakage across scenarios.
• Constitution-friendly refactorability: Defines what starter must provide (layering bones and seams) so refactors aligned with ${DEV_CONSTITUTION_PATH} can proceed without starter blockages.
• Cost allocation rules: Keeps Red worker cost focused on legal red lamps, Green on product behavior, and Refactor on constitution-driven structure changes.
• Predictable gap classification: Forces missing capabilities to be recognized as feature-specific product gaps rather than disguised starter costs.

Quick Start

Apply the starter stableness principle to your feature package so that Red, Green, and Refactor can run with deterministic isolation using the required runner, probes, fixtures, and constitution-aligned structure.