scoped-implementation

Scoped implementation executes targeted code changes strictly within predefined boundaries from an implementation-plan document. It enforces a safety contract to prevent scope creep, ensuring no system modifications occur outside the explicitly allowed acceptance criteria.

A frozen slice is a pre-defined software feature with explicit boundaries and acceptance tests. Scoped implementation processes this slice by adhering strictly to the plan, preventing unintended changes and maintaining safety contract adherence throughout the development process.

To execute scoped code implementation, run the skill directly on your implementation-plan file, such as 'plan-FeatureXYZ.md'. The skill reads the predefined boundaries and acceptance criteria from the document to perform the targeted implementation safely.

Yes, boundary enforcement is applied automatically during implementation. The skill ensures strict adherence to the safety contract, guaranteeing that no code or system changes occur beyond what is explicitly allowed by the acceptance criteria.

No external dependencies are required to use scoped implementation. The skill operates independently to process your implementation-plan file and execute the feature implementation within the set constraints of your acceptance criteria.

Scoped implementation should not be used when a task lacks a predefined implementation plan or explicit acceptance criteria. It is designed specifically for executing frozen slices, so exploratory programming or tasks requiring dynamic scope expansion are not suitable.