New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Piv Slice Epic

by coleam00 in coleam00/skills

Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local).

MITAuto-check passedProduct & Project Management

Install Piv Slice Epic

skills CLI
$ npx skills add coleam00/skills --skill piv-slice-epic -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coleam00/skills piv-slice-epic --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/piv-slice-epic .claude/skills/piv-slice-epic && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
piv-slice-epic
GitHub stars
676
Token cost
~1.5k tokens
SKILL.md length
749 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local).

  • Works in 5 steps: Read the sources → Orient on the code surface (if not… → Decompose into PIV-sized slices → …
  • Product & Project Management work in your project
  • SKILL.md covers Input, Process, Output and Notes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Piv Slice Epic is an agent skill from coleam00/skills. Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local). Accepts the epic and its architecture as one doc or as an epic plus a separate linked architecture page. Turns a large strategic doc into the discrete units of work that the PIV loop consumes.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. It works with Model Context Protocol, Jira and GitHub. The repository describes itself as: The agent skills I actually use to build software with coding agents. The PIV loop, planning, worktrees, and the meta-skills for building your own AI Layer. The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “/piv-slice-epic”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Read the sources
  2. Orient on the code surface (if not already primed)
  3. Decompose into PIV-sized slices
  4. Slice for parallelizability
  5. Write the ticket breakdown

What it can do on your machine

Read from SKILL.md and the folder at commit 847be08. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Piv Slice Epic loads about 1.5k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 749 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coleam00/skills at commit 847be08, republished under its MIT licence (© coleam00). 749 words, ~1,548 tokens.

Download SKILL.mdSave it as .claude/skills/piv-slice-epic/SKILL.md (or your agent's skills folder).
name
piv-slice-epic
description
Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local). Accepts the epic and its architecture as one doc or as an epic plus a separate linked architecture page. Turns a large strategic doc into the discrete units of work that the PIV loop consumes.
argument-hint
[epic + its linked architecture page (paths or Confluence/Jira URLs); a PRD for greenfield]

/piv-slice-epic — Slice an Epic into PIV-Sized Tickets

The bridge between a strategic doc and the PIV loop. The epic doc is the destination; the PIV loop is the unit of motion; tickets are the bridge. /piv-slice-epic does the slicing.

Input

  • $ARGUMENTS — the epic to slice and its architecture decisions. These arrive as one doc or two:
    • a single architected epic that carries its own ## Architecture section, or
    • an epic plus a separate, linked architecture page (the common case when the architecture lives beside the epic — e.g. a Confluence epic page and its linked architecture page, both passed as URLs). Read both.
    • greenfield: a PRD stands in for the epic. When the inputs are tracker references (Confluence/Jira URLs or keys), fetch them from the source via the Atlassian MCP. This is the load-bearing input: the architecture names the seams, data model, and missing pieces the slices must respect.
  • Not prime-dependent. A primed session helps, but isn't required. If the codebase surface isn't loaded, this skill orients itself (Step 2) before slicing.

Process

Step 1 — Read the sources

Read the epic fully (goal, user stories, acceptance criteria, out-of-scope) and its architecture decisions, whether they are an ## Architecture section on the epic or a separate linked page (the approach, stack, data model, missing pieces, spikes). If the architecture is a separate page, fetch and read it too. The slicing has to respect those calls.

Step 2 — Orient on the code surface (if not already primed)

Slicing needs enough codebase awareness to judge what's independent vs dependent — file overlap, shared seams. If the session is already oriented, skip this. Otherwise explore it yourself — don't depend on a prior /prime-codebase: starting from the architecture's named seams, data model, and missing pieces, read the relevant files/dirs (e.g. the adapter interface, the orchestrator, the ingestion pipeline) to see what exists, what's reused, and where new code lands. Just enough to slice confidently — not a full re-derivation.

Step 3 — Decompose into PIV-sized slices

Break the epic into tickets. Scope these for AI, not for a human backlog — an agent loop carries far more than a traditional ticket: a small-to-medium implementation phase, ~8–10 subtasks, often 500–1500 lines of change (20–50% tests). A small epic might even be a single ticket. A well-sized ticket:

  • Is one testable concern — easy to test, review, and prove on its own.
  • Is one coherent unit — a vertical slice of behavior, not a horizontal layer.
  • Has clear acceptance criteria of its own.
  • Is small enough that one focused loop can one-shot it without context rot — not so large the agent loses the thread and returns diminish.

Split by dependency, by concern, or as a slim end-to-end slice (prove the whole flow thinly, then fatten it next loop) — whatever makes each ticket easiest to prove. If a slice is too big to test or review in one honest pass, split it further. The planning detail stays high regardless — it's the scope that's larger.

Show full SKILL.md (262 more words)Show less
Step 4 — Slice for parallelizability

Map dependencies between tickets. Independent tickets — ones that don't touch the same files or rely on each other's output — can run in parallel worktrees (see /worktree-create). Mark which tickets are independent and which form a dependency chain. Slicing along vertical-slice-architecture seams maximizes independence.

Plan just-in-time: a dependent ticket waits until its dependency is implemented, not just sliced — building the dependency informs the dependent's plan, so planning it early plans against a guess. Independent tickets can be planned and run in parallel; dependent ones wait their turn.

Step 5 — Write the ticket breakdown

Write the tickets to your tracker (Jira via the Atlassian MCP, Linear, GitHub Issues, Archon's tasks) — or to a local docs/tickets/<epic-slug>.md if you're solo or have no tracker. Either way, every ticket carries its own context — that's what lets a loop pick it up later without re-reading the whole epic:

# Ticket Breakdown — <epic name>

## Epic summary — goal in 2-3 lines
## Tickets
   ### TICKET-1 — <title>
   - Scope / acceptance criteria — one testable concern
   - Per-ticket context: the doc sections, guides, and seams this ticket needs
     (e.g. "source-adapter guide · seam: adapter interface · AC #2 + #4 from the epic")
   - Files touched (estimate) · rough size (~500–1500 lines, incl. tests)
   - Depends on: <none / TICKET-x>
   ### TICKET-2 — ...
## Dependency graph
   <text or mermaid graph showing the order + parallel groups>
## Suggested execution order
   Wave 1 (parallel): TICKET-1, TICKET-3
   Wave 2: TICKET-2 (after TICKET-1 is implemented)

Output

A ticket breakdown in your tracker (or docs/tickets/<epic-slug>.md). Each ticket then enters its own PIV loop — straight to /piv-plan-implementation if it's well-scoped (it primes what it needs), or /prime-codebase first if it needs more codebase orientation. Priming is optional; the per-ticket context above is what makes that possible.

Notes

  • Issue management is tool-agnostic: Jira (via Atlassian MCP), Linear, Notion, GitHub Issues, Archon's tasks — or just a folder of markdown files if you're solo. The tracker doesn't matter; the goal is to split the work just enough that each loop has the highest chance of one-shot success, so you can automate the loop.
  • Greenfield: the same slicing applies to MVP phases instead of epic tickets.

© coleam00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/piv-slice-epic of coleam00/skills.

Open the folder on GitHubat commit 847be08

Compare with similar skills

Piv Slice Epic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Piv Slice Epic compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Piv Slice Epic this skillcoleam00/skills676—~1.5kAutomated safety check: PassMIT
Daily Meeting Updatedavila7/claude-code-templates33k2 repos~3kAutomated safety check: PassMIT
Integration Orchestratorrampstackco/claude-skills945—~5.3kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k—~5.7kAutomated safety check: PassMIT
Link Ticket To SessionJayantDevkar/claude-code-karma329—~1.8kAutomated safety check: NotesApache-2.0
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Daily Meeting Update

    davila7/claude-code-templates

    Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 2 repos~3k tokens
    Product & Project ManagementAuto-check passed

  • Integration Orchestrator

    rampstackco/claude-skills

    Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's…

    945 GitHub stars~5.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Link Ticket To Session

    JayantDevkar/claude-code-karma

    Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.

    329 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Jira Natural Language Interface

    jjmartres/opencode

    Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed

  • Issue Triage Loop

    cobusgreyling/loop-engineering

    Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.

    11k GitHub stars~522 tokensUpdated today
    DevelopmentAuto-check passed

More from coleam00/skills

All 34 skills in this repo

  • Ablate AI Layer

    coleam00/skills

    Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what…

    676 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed

  • Build Dark Factory

    coleam00/skills

    Take a PRD and build a dark factory around it - a repository that takes work in as an issue and ships validated code out with nobody at the keyboard - one component at a time, into the user's actual…

    676 GitHub stars~12k tokensUpdated 3 days ago
    Auto-check passed

  • Drive Screen

    coleam00/skills

    Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals.

    676 GitHub stars~5.4k tokensUpdated 3 days ago
    Auto-check passed

  • Second Brain Audit

    coleam00/skills

    Audit any second brain, notes folder, or agent memory for facts that have quietly stopped being true, then fix the worst one so it stops recurring.

    676 GitHub stars~4.6k tokensUpdated 3 days ago
    Auto-check passed

  • Build Signal Engine

    coleam00/skills

    Build a personal signal engine from scratch - a system that reads every source someone cares about each day (changelogs and release notes, communities, feeds, videos, papers), makes a quick decision…

    676 GitHub stars~2.9k tokensUpdated 3 days ago
    Auto-check passed

  • Worktree Create

    coleam00/skills

    Create one or more git worktrees for parallel development, each on its own branch with gitignored config copied in, dependencies installed, and a health check, by fanning out a setup subagent per…

    676 GitHub stars~958 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Piv Slice Epic

What does Piv Slice Epic do?

Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local). Piv Slice Epic is an agent skill from coleam00/skills. Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local).

When should I use Piv Slice Epic?

Piv Slice Epic fits situations like: product & Project Management work in your project.

How do I install Piv Slice Epic in Claude Code?

Run `npx skills add coleam00/skills --skill piv-slice-epic -a claude-code`. Or copy the skill folder (.claude/skills/piv-slice-epic in coleam00/skills) into .claude/skills/piv-slice-epic in your project. Claude Code loads it when a task matches its description.

How do I install Piv Slice Epic in Codex?

Run `npx skills add coleam00/skills --skill piv-slice-epic -a codex`. Or copy the skill folder (.claude/skills/piv-slice-epic in coleam00/skills) into .agents/skills/piv-slice-epic in your project. Codex loads it when a task matches its description.

Can I use Piv Slice Epic in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coleam00/skills --skill piv-slice-epic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/piv-slice-epic, .gemini/skills/piv-slice-epic, .github/skills/piv-slice-epic and .opencode/skills/piv-slice-epic in your project.

What does Piv Slice Epic need to run?

SKILL.md names no scripts, command-line tools or credentials: Piv Slice Epic is instructions for the agent only.

Does Piv Slice Epic access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Piv Slice Epic safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Piv Slice Epic use?

Piv Slice Epic is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Piv Slice Epic use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Piv Slice Epic?

Skills that share tags, products or a category with Piv Slice Epic: Daily Meeting Update (davila7/claude-code-templates, 33k stars), Integration Orchestrator (rampstackco/claude-skills, 945 stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars) and Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Piv Slice Epic?

coleam00 (a GitHub user) maintains it in coleam00/skills, which has 676 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: coleam00/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.