j.pi-plan
Skill0 starsChanged 23 days agoApache-2.0View on GitHub
Define or expand project Epics in PROJECT_SUMMARY.md. Use this at the start of a project to establish its foundation, AND whenever the user wants to add major new features, plan a significant new area of work, or make epic-level changes to an existing project. Trigger whenever you hear things like "new feature area", "big change", "new epic", "expand the project", "add a major capability", or "plan a new phase" — even mid-project.
In this repository151 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- j.brainstormSkill
- j.breakSkill
- j.btwSkill
- j.check-inSkill
- j.clearifySkill
- j.close-storySkill
- j.cloud-connectSkill
- j.commitSkill
- j.connectSkill
- j.continueSkill
- j.conventionsSkill
- j.dashboard-shareSkill
- j.dashboardSkill
- j.deep-diveSkill
- j.distributeSkill
- j.docSkill
- j.doc-syncSkill
- j.doooSkill
- j.doSkill
- j.jenga-configSkill
- j.jenga-permission-levelSkill
- j.jengaSkill
- j.errorSkill
- j.evaluateSkill
- j.examplifySkill
- j.gitignoreSkill
- j.helpSkill
- j.ideaSkill
- j.improveSkill
- j.initSkill
- j.jbpSkill
- j.lgtmSkill
- j.playbook-newSkill
- j.playbookSkill
- j.proceedSkill
- j.publishSkill
- j.reconcile-originSkill
- j.reconcileSkill
- j.redoSkill
- j.skillifySkill
- j.smoke-testSkill
- j.spinoffSkill
- j.statusSkill
- j.testSkill
- j.todoSkill
- j.toolsSkill
- j.unchartedSkill
- j.wtfSkill
- skill-nameSkill
- j.brainstormSkill
- j.breakSkill
- j.btwSkill
- j.check-inSkill
- j.clearifySkill
- j.close-storySkill
- j.cloud-connectSkill
- j.commitSkill
- j.connectSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Existing project: Add one or more new Epics to an existing PROJECT_SUMMARY.md when the user wants to plan a major new area of work.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pi-plan — Define and Expand Project Epics
skills/j-pi-plan/ is the canonical, hand-edited directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the E50 reopening of 2026-09-09, which promoted skills/j-pi-plan/ from generated twin to sole canonical form). The j- prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see project/documentation/skill-authoring.md's "Invocation Convention").
⚠️
scripts/generate-j-alias.shwas retired byE50_S14and no longer exists — there is nothing to run. This file was previously generated from a bareskills/pi-plan/SKILL.mdsource;E50_S15deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
When to use this skill
- New project: Gather project description and goals, then define the initial set of Epics.
- Existing project: Add one or more new Epics to an existing
PROJECT_SUMMARY.mdwhen the user wants to plan a major new area of work.
Detect which mode you're in by checking whether project/PROJECT_SUMMARY.md already exists and has Epics defined.
Mode 1: New Project
- Gather project info — Ask the user for:
- Description: A high-level explanation of what the app or service does (an "elevator pitch").
- Goals: What specific problem(s) the project is intended to solve. Be clear about the desired outcome.
- Clarify scope — If the responses are unclear or lack sufficient detail, ask clarifying questions. The goal is a broad understanding — avoid delving into granular details unless they directly impact the core idea.
Define Epics — Using the description and goals, define the Epics section of
project/PROJECT_SUMMARY.md. Each Epic is a JSON object:- title: Concise title for the Epic.
- short_description: Brief explanation of what this Epic aims to achieve.
- date_added: Today's date (YYYY-MM-DD).
- date_started: Set to
nullinitially. - related_stories: Empty array
[]initially.
Example: ./assets/epic.json.
Story files created under project/board/stories/ should follow ./assets/story_template.md.
Mode 2: Existing Project — Adding New Epics
- Read the existing file — Load
project/PROJECT_SUMMARY.mdto understand the current project context and existing Epics. This prevents duplication and ensures new Epics are coherent with what's already there. - Understand the new scope — Ask the user:
- What is the new capability, feature area, or phase they want to add?
- What problem does it solve, or what goal does it serve?
- Are there any dependencies on existing Epics?
- Clarify if needed — Same as Mode 1: ask follow-up questions if the scope is vague, but stay high-level.
- Define new Epics — Draft one or more new Epic objects using the same schema as above, then append them to the existing Epics list in
project/PROJECT_SUMMARY.md. Do not modify existing Epics unless the user explicitly asks. - Confirm before writing — Show the user the proposed new Epic(s) and get confirmation before updating the file.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

