Skip to content
Skills Library
Management & product · Planning

pc-create

/pc-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.

Repository
planchunk ↗
Licence
MIT
Last repository change
30.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Steps
Original SKILL.md headings · 27 lines, 213 words
SKILL.md preview
---
name: pc-create
description: 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.
---

# pc-create

Create a plan that one person or agent can run in small pieces, one session per chunk.

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

## Steps

1. Read `RULES.md` and `FORMAT.md`.
2. Read the repo's AGENTS.md and CLAUDE.md. Read `plans/KNOWLEDGE.md` if it exists.
3. Ask the user short questions only if the goal, limits, or success checks are unclear. Read the code that the goal touches.
4. Pick a slug. If `plans/<slug>/` exists, stop and ask.
5. Draft the chunk table (ID, title, repo, depends on, outcome). Check:
   - Each chunk fits one session (5 to 10 steps, a few files).
   - Each chunk leaves the repo working.
   - Dependencies have a valid order.
6. Show the goal and the chunk table to the user. Wait for approval.
7. Write `PLAN.md` and one file per chunk from the templates. In each chunk:
   - List exact files and symbols under "Context needed".
   - Put the repo's real check commands under "Acceptance checks".
   - Add "Out of scope" so the session stays inside the chunk.
8. Create or update `plans/README.md` and, if missing, `plans/KNOWLEDGE.md`.
9. Tell the user: the plan path, the chunk count, and that the next step is `pc-next` in a fresh session.

Do not write source code. Do not commit.

Versions

The database has no other skills named pc-create.

Database snapshot: 13.11.2026 · package version baa6814041e3 (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-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.
  • 90pc-split
    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.
  • 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.…
  • 90create-plan
    Interviews the user and writes an implementation plan for the current request. Use when the user names /create-plan or asks for an implementation plan of this feature.
  • 100planning-and-task-breakdown
    Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode".
  • 100feature-spec-breakdown
    Breaks a feature spec and its plan into small, independent vertical-slice tickets saved as Markdown files, checks coverage against both, reviews tickets one by one, then optionally creates todos or publishes to a tracker the user names. Use when asked to break down, split, or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.