slice-the-spec

Converts a PRD into vertically sliced GitHub issues with dependencies and HITL/AFK flags.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill slice-the-spec-bing0116-gif
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slice-the-spec
Source: https://github.com/BING0116-gif/math-AI-assistant/tree/main/.agents/skills/slice-the-spec
Command: npx skills add https://github.com/BING0116-gif/math-AI-assistant --skill slice-the-spec-bing0116-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished PRD into an actionable backlog is slow and error-prone: teams often create horizontal, layer-by-layer tasks that block parallel work and hide integration risks until late. This Skill transforms a clarified PRD into a small set of end-to-end vertical slices, each ready to become a GitHub issue. ## Core Features & Use Cases - Vertical Slice Generation: Breaks a PRD into tracer-bullet issues that cut through data, domain, API, and UI layers instead of horizontal tasks. - HITL/AFK Classification: Flags each issue as requiring human decisions (HITL) or safe for autonomous agent implementation (AFK). - Dependency Mapping: Defines blocked-by relationships between slices and identifies at least one immediately startable issue. - Use Case: After drafting a PRD for a weekly summary email feature, run this Skill to get 3-5 GitHub-ready issues with acceptance criteria, dependencies, and reviewer notes that multiple engineers or agents can pick up in parallel. ## Quick Start Ask the assistant to slice the current PRD into GitHub-ready issues using the slice-the-spec workflow.

Frequently Asked Questions about slice-the-spec

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

FAQPage Schema
How do I turn a PRD into GitHub issues?▼

Provide the clarified PRD and let the Skill locate it, explore the codebase, and draft vertical slices. It then quizzes you on granularity and dependencies before emitting GitHub-ready issue bodies with acceptance criteria.

What is a vertical slice in agile backlog planning?▼

A vertical slice is a thin end-to-end piece of functionality crossing all layers (data, domain, API, UI) rather than one layer in isolation. This Skill prefers such tracer-bullet slices over horizontal tasks like setting up database tables alone.

What is the difference between HITL and AFK issues?▼

HITL issues require human-in-the-loop decisions such as design reviews or stakeholder sign-off, while AFK issues are safe for an autonomous agent to implement and merge. The Skill flags every slice explicitly and prefers AFK when risk is low.

When should I not use PRD slicing for backlog creation?▼

Avoid it when requirements are still fuzzy or no PRD exists, since the Skill depends on a clarified spec. In that case, run clarification and spec-writing steps first, or it will ask targeted questions instead of guessing.

Does the Skill create the GitHub issues automatically?▼

It generates GitHub-ready Markdown issue bodies including context, tasks, acceptance criteria, and links, ready to paste or create via API. It can optionally group them into epics or labels when repository conventions are clear.