Defines and expands project Epics in PROJECT_SUMMARY.md for scrum-based planning.
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-pi-plan-samwelmunga
Please help me install this Agent Skill. Skill: j.pi-plan Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-pi-plan Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-pi-plan-samwelmunga
project/PROJECT_SUMMARY.md using a structured JSON schema. - Existing project expansion: Reads the current PROJECT_SUMMARY.md, then appends new Epics for major feature areas without modifying existing ones, with user confirmation before writing. - Collision-safe invocation: Acts as a polyfill alias of the pi-plan skill so the flow remains reachable even when a host tool's built-in command shadows the bare /pi-plan name. - Use Case: Mid-project, you decide to add a major new capability like a reporting module. Invoke this Skill to draft a new Epic with title, description, and dates, confirm it, and append it to the project summary. ## Quick Start Ask the agent to run j.pi-plan to add a new epic for the reporting module to the project summary.High-intent search queries and answers about installing and using this skill.
Invoke the skill and describe the new capability or feature area. It reads your existing PROJECT_SUMMARY.md, drafts new Epic objects matching the established schema, shows them for confirmation, and appends them without altering existing Epics.
Provide a high-level description of what the app does and the goals it should achieve. The skill asks clarifying questions if the scope is vague, then defines the initial set of Epics in project/PROJECT_SUMMARY.md.
They are behaviorally identical. j-pi-plan is a polyfill alias that guarantees the flow stays reachable when a host tool's built-in command shadows the bare /pi-plan name, since skill resolution is a literal directory-name match.
Each Epic is a JSON object with title, short_description, date_added, date_started (initially null), and related_stories (initially an empty array). A template is provided in the skill's assets/epic.json file.
Skip it for small, granular work like single bug fixes or minor tasks. Epic planning is meant for major feature areas, new phases, or significant capabilities; smaller units belong in stories and tasks under an existing Epic.
ed3daiIdentify and resolve contradictions in user requirements to align design goals.
samwelmungaExecute structured development tasks from a scrum board with agent handoffs.
GenEducationSummarizes sprint progress and flags delivery risks from sprint status records.
thepradipOrganize Jira issues, sprints, and workflows with JQL-based reporting.