slice-spec

Files (2)

• SKILL.md
• slice-template.md · references/

SKILL.md (first lines)

# Slice Spec

Split only when splitting increases delivery speed or feedback quality.

1. Read the parent spec and inspect enough of the repository to understand real seams.
2. If the work is one coherent deliverable that fits a single implementation session, say that slicing is unnecessary and stop without creating files.
3. Otherwise create end-to-end vertical slices. Each slice should produce observable behavior and its own verification signal.
4. Prefer risk-first tracer bullets that validate uncertain contracts early. Do not default to separate frontend, backend, database, or test-only slices.
5. Declare blocking edges explicitly and keep independent slices parallelizable.
6. Preserve cross-layer contract ownership and compatibility in every affected slice.

Write files beside the parent spec, normally `.scratch/<feature>/slices/01-<slug>.md`, using [references/slice-template.md](references/slice-template.md). Follow an existing local convention when one exists. Do not create an issue tracker, task state machine, journal, or implementation.

Report the dependency order, why each boundary is useful, and the recommended first slice. The next action is direct implementation unless the user explicitly chooses another workflow.

From JobsHwang/skills, MIT.

More from JobsHwang/skills