What problem does it solve?
When executing a phased software delivery plan iteratively, it is easy to lose track of which TDD slices are done and which comes next. This Skill reads plans from .stencila/plans/, records the just-completed slice, and deterministically selects the next execution unit based on phase ordering and dependency constraints.
Core Features & Use Cases
- Completion Tracking: Appends the just-finished slice or slice batch to the completed slices list, accepting comma-separated strings or JSON arrays.
- Next Slice Selection: Walks phases and slices in order, respects explicit dependencies, and validates package references against the codebase with glob and grep.
- Granularity Normalization: Combines adjacent, small, same-package slices into one execution unit to reduce workflow overhead while keeping a tractable Red-Green-Refactor cycle.
- Use Case: During a TDD-driven feature build, after finishing "Phase 1 / Slice 2", invoke the Skill to record completion and receive "Phase 1 / Slice 3" with its scope, acceptance criteria, and packages.
Quick Start
Mark "Phase 1 / Slice 2" as completed and select the next slice from the delivery plan in .stencila/plans/.