slice

Break a settled grill-session into a parent PRD and tracer-bullet child issues.

16|9|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/sonthanh/brain-os-plugin --skill slice-sonthanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice
Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/slice
Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill slice-sonthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Breaks a settled grill-session, plan, or PRD into a parent story (PRD body) and independently-grabbable tracer-bullet children. It ensures each child carries ## Parent and ## Blocked by references; the parent body holds the auto-filled sub-issues checklist that downstream skills reference for DAG drainage. Use when you want to convert a grill outcome into AFK/HITL implementation tickets, file slices to sonthanh/ai-brain, or break a plan down for parallel execution.

Core Features & Use Cases

  • Synthesizes a PRD from a grill-session and creates a parent GitHub issue on ai-brain with a PRD body and a placeholder children checklist.
  • Emits independently-grabbable child issues with ## Parent + ## Blocked by references; supports DAG drainage via /impl story.
  • Applies tracer-bullet slicing so each child represents end-to-end capability and is independently verifiable.
  • Enforces a review gate: the parent PRD must be approved before creating children; children reference the parent and blockers.

Quick Start

Run /slice on a settled grill-session to generate a parent PRD and a set of tracer-bullet child issues.

Frequently Asked Questions about slice

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

FAQPage Schema
How do I turn a grill session into PRD-backed GitHub issues?

To turn a grill session into PRD-backed GitHub issues, run /slice on the settled session. It synthesizes a parent PRD body with a placeholder children checklist and creates independently-grabbable child issues with Parent and Blocked by references.

How does tracer-bullet slicing work for parallel workflow execution?

Tracer-bullet slicing works by breaking a plan into child issues representing end-to-end capabilities. Each slice is independently verifiable and carries dependency references, enabling DAG-driven topological ordering for parallel execution and staged review.

Can I use slice to manage DAG dependencies on GitHub parent and child issues?

Yes, you can use slice to manage DAG dependencies on GitHub issues. It enforces topological ordering for issue creation, requiring children to declare observable surfaces and Blocked by references before linking them to the approved parent PRD.

Do I need an approved parent PRD before creating child issues?

Yes, an approved parent PRD is required before creating child issues. Slice enforces a review gate where the parent story body must be approved first, ensuring children can properly reference the parent and blockers before creation.

What is the best way to break down a plan for parallel execution using GitHub automation?

The best way to break down a plan for parallel execution is using tracer-bullet slicing. It converts a settled plan into a parent PRD with a sub-issues checklist and child issues with dependency declarations, enabling DAG drainage and independent verifiability.

Why does slice require topological ordering when creating child issues?

Slice requires topological ordering when creating child issues to enforce DAG-driven dependency management. This ensures children are generated with correct Blocked by references and observable surfaces, preventing execution blockers during parallel staging.