slice

Slice

Use roadmap to deepen one area inside the canonical design. A slice is a scoped design view, not a separate planning process.

Workflow

Load ../roadmap/SKILL.md and ../roadmap/references/roadmap-schema.md.
Read the parent roadmap or legacy design and the named area.
Run repository recon for that area before asking anything.
Reuse settled parent decisions. Ask only a newly discovered blocking question; do not restart the interview or exceed Roadmap's five-question planning-round cap.
Add or revise a subsection under ## 6. Design.
Re-run the ponytail and rubber-duck checks for affected decisions.
Stop before task generation.

If the user provides an existing slice file, maintain it and link it from the roadmap rather than forcing a migration.
For new work, do not create separate slice files by default.
Preserve unrelated design sections and all consumed-task history.

One named area per invocation.
Smallest end-to-end version that satisfies the parent outcome wins.
Name concrete paths, symbols, inputs, outputs, and reused patterns.
Do not invent categories that the area does not need.
No code, task lists, speculative extension points, or repeated product discovery.