software-slice-selection

Selects the next unfinished execution slice from a phased software delivery plan.

902|58|Updated May 31, 2012
One-click install
npx skills add https://github.com/stencila/stencila --skill software-slice-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-slice-selection
Source: https://github.com/stencila/stencila/tree/main/.stencila/skills/software-slice-selection
Command: npx skills add https://github.com/stencila/stencila --skill software-slice-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

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/.

Frequently Asked Questions about software-slice-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I select the next TDD slice from a delivery plan?

Provide the just-completed slice name and the list of already-completed slices. The Skill parses the plan in .stencila/plans/, walks phases and slices in order, skips completed ones, and returns the next execution unit with scope, acceptance criteria, and packages.

How does slice completion tracking work across iterations?

Pass the completed slices list as a comma-separated string or JSON array on each invocation. The Skill appends the just-finished slice, avoids duplicates, and returns the updated list in the same format for the next iteration.

Can adjacent plan slices be combined into one execution unit?

Yes, adjacent unfinished slices in the same phase are combined when they touch the same package, are small and closely related, and have no dependency boundary requiring independent validation. Combinations never cross phase boundaries.

Does this Skill verify plan-level Definition of Done items?

No. It only determines slice exhaustion, meaning whether more execution slices remain. When all slices are complete, it notes that Definition of Done checks such as passing tests and linting must be verified separately.

What happens if no delivery plan exists in the repository?

The Skill reports an error that no plan was found in .stencila/plans/ and does not fabricate one. A plan file must exist before slice selection can begin.

What if a slice references a package that no longer exists?

The Skill validates package references using glob and grep against the codebase. Stale references are noted in the scope description as a warning, but selection is not blocked since they can be resolved during implementation.