What problem does it solve?
When a large feature is decomposed into vertical slices, each slice still needs its own focused architecture design before implementation can begin. Doing this manually for every slice is slow and inconsistent, and doing it all at once produces shallow designs. This Skill designs exactly one slice in isolation, producing a structured design doc that downstream synthesis and implementation steps can consume.
Core Features & Use Cases
- Single-slice design: Reads a slice map under
.rpiv/artifacts/slices/, locates the named slice, and decides its approach, file map, key interfaces, integration points, and success criteria.
- Upstream contract awareness: Accepts
--upstream design docs from a design fanout and builds against their decided Key Interfaces instead of redesigning dependencies.
- Structured output: Writes a frontmatter-tagged design doc to
.rpiv/artifacts/designs/ with status tracking, consumed later by a synthesize step and graded by a review panel.
- Use Case: A design fanout dispatches this Skill once per slice in parallel; each run reads only its slice's footing, asks the user only on genuine blocking design forks, and emits a ready-status design doc.
Quick Start
Run the design-slice skill with the path to your slice map and the slice identifier, for example ".rpiv/artifacts/slices/auth.md Slice 2: token refresh", to generate that slice's design document.
