pc-split

What it does and when to use it

Split a chunk that is too big into two or more smaller chunks and renumber the plan. Use when a chunk will not fit in one session, or when a session is running out of room.

How it works

1. Steps

---
name: pc-split
description: Split a chunk that is too big into two or more smaller chunks and renumber the plan. Use when a chunk will not fit in one session, or when a session is running out of room.
---

# pc-split

Make a chunk smaller without losing work or order.

Shared files: `~/.planchunk/core/RULES.md`, `~/.planchunk/core/FORMAT.md`, `~/.planchunk/core/templates/chunk.md`.

## Steps

1. Read `RULES.md` and the repo's AGENTS.md and CLAUDE.md.
2. Read `PLAN.md` and the chunk to split (the one the user names, else the `in-progress` chunk).
3. Find the split points. Each new chunk must:
   - Have 5 to 10 steps at most and one clear result.
   - Leave the repo working (checks pass).
   - Keep the dependency order.
4. If the chunk is `in-progress`, put the steps already done (`[x]`) in the first new chunk and mark it `done` only if its checks passed. Put the rest in the later chunks.
5. Show the user the new chunk table rows and which steps go where. Wait for approval.
6. Write the new chunk files from the template. Give each one its own context, acceptance checks, and out of scope. Copy the handoff notes to the chunk they belong to.
7. Renumber later chunks if needed. Fix `Depends on`, `Unblocks`, and every link. Do not leave two chunks with the same ID.
8. Update the chunk table in `PLAN.md`. Add a change log line: what was split and why.
9. Tell the user the new chunks and that the next step is `pc-next`.

Do not edit source code. Do not drop steps or notes. Do not commit.

Versions

The database has no other skills named pc-split.

Database snapshot: 13.11.2026 · package version c448606f6368 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 90pc-create
  Create a new implementation plan split into small chunks, so each chunk fits one session. Use when the user wants a plan, spec, or breakdown for a large task. Writes plans/<slug>/PLAN.md and chunk files.
• 90pc-convert
  Convert an existing plan that does not follow the planchunk format (a Markdown plan, pasted text, or a tool plan file) into PLAN.md plus small chunk files. Use when a plan already exists but is one big document.
• 82divide
  Split a GitHub issue or task into session-sized issues and put them on the board. Use when a task is too big for one session or remaining work must be split off.
• 100sprint
  Use when one milestone is too large for a single specification or plan and must ship as several ordered stages across sessions.
• 88wayfinder
  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker. Resolves them one at a time until the way to the destination is clear. Produces decisions, not deliverables. The map is an index, not a store. Tickets are…
• 100chunk-plan
  Decompose a non-trivial implementation task into independently-deliverable, verifiable chunks before spawning the-coder. Use when the user says 'plan the implementation', 'break this into chunks', 'create a coding plan', or before any task too large for a single coding session.…