Product requirements and issue slicing

Skill wfprieto/wcbs-build-kit/skills/product-requirements-and-issue-slicing

Use when converting ideas, audits, requests, strategy notes, PRDs, specs, or implementation plans into product requirements and vertical issue slices with independent acceptance criteria, exact evidence, non-goals, dependencies, and APIVR-ready execution order.From its SKILL.md

Install

npx -y skills add wfprieto/wcbs-build-kit --skill product-requirements-and-issue-slicing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

Product Requirements And Issue Slicing

Use this skill when a plan is too large or needs to become executable issues.

Slicing Rules

Slice vertically by user-visible or system-verifiable outcome.
Each slice must have one owner, one evidence path, and one rollback story.
Avoid horizontal slices such as "build models", "build API", then "build UI" unless each is independently verifiable.
Put risky learning slices early.
Keep non-goals explicit to prevent scope drift.

Issue Template

Title:
Objective:
User/system outcome:
In scope:
Out of scope:
Files likely affected:
Acceptance criteria:
Tests/evidence:
Rollback:
Dependencies:
APIVR tier:

Worked Example

Scenario: Build subscription analytics.

Slice 1: define canonical subscription states and glossary.
Slice 2: produce one verified monthly churn query.
Slice 3: render admin table with empty/error/export states.
Slice 4: add scheduled email after report accuracy is verified.
Each slice can be tested and released independently.

Workflow

Turn approved requirements into vertical slices with user-visible acceptance evidence, dependency order, and an explicit out-of-scope boundary.