One-click install
npx skills add https://github.com/steve-piece/bytheslice --skill cook-pizzas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cook-pizzas
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/cook-pizzas
Command: npx skills add https://github.com/steve-piece/bytheslice --skill cook-pizzas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of fragmented, unmanageable software development by decomposing complex Product Requirement Documents (PRDs) into a structured, two-level roadmap of Pies and Slices, ensuring every deliverable is coherent and autonomous.

Core Features & Use Cases

  • Two-Level Decomposition: Automatically breaks down PRDs into Pies (3-8 slice chapters) and Slices (vertical deliverables), creating a clear, actionable development path.
  • Workflow Orchestration: Uses parallel subagent writers to generate plan files, ensuring consistency and speed while maintaining strict schema validation.
  • Use Case: When starting a new project, use this Skill to convert your high-level feature brief into a complete master checklist, project rules file, and individual slice plans, ready for immediate execution.

Quick Start

Run the cook-pizzas command to decompose your finalized PRD into a complete roadmap of pies and slices.

Frequently Asked Questions about cook-pizzas

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

FAQPage Schema
How do I decompose a product requirement document into a development roadmap?

To break down a PRD into a development roadmap, decompose requirements into structured Pies and vertical Slices. This Skill automates PRD decomposition by orchestrating subagents to generate validated plan files and a master checklist, ensuring tasks are manageable and testable.

What is vertical slice decomposition in software project planning?

Vertical slice decomposition is a planning technique that breaks product requirements into autonomous, deliverable Slices grouped into chapter Pies. It ensures every development task is coherent, testable, and aligned with architectural standards during the initial project planning phase.

Do I need a finalized PRD before creating an ordered project roadmap?

Yes, a finalized PRD is required before creating an ordered roadmap. The decomposition process relies on complete product requirements to accurately break the project down into Pies and vertical Slices and generate validated plan files.

How do I generate a master checklist from a PRD for software engineering tasks?

You can generate a master checklist from a PRD by running the decomposition command, which uses parallel subagent writers to process the requirements. This produces a complete master checklist, project rules file, and individual slice plans ready for execution.

Can I use this PRD decomposition approach for complex software architecture planning?

Yes, you can use this approach for complex architecture planning. It decomposes requirements into a two-level roadmap ensuring every deliverable is autonomous and aligned with architectural standards, making it suitable for managing intricate software engineering projects.