plan

Create structured implementation plans from GitHub issues and repository context.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill plan-jeqqe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/plan
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill plan-jeqqe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly implementation churn by turning an issue or request into a structured, scope-aware plan before any non-trivial work begins.

Core Features & Use Cases

  • Context-first planning: Reads project and agent memory files to ground the plan in existing goals, constraints, and open questions.
  • Issue comprehension: Fetches specific GitHub issues (by number) and uses linked context to avoid mis-scoping.
  • Guardrails and unknowns: Checks MVP scope, architecture decisions, security and layer boundaries, then explicitly marks missing or unclear information.
  • Actionable plan output: Produces a conversation-only plan covering approach by layer and an effort estimate, with no files written.

Quick Start

Use /skill:plan 1234 to convert GitHub issue 1234 into a structured implementation plan grounded in the latest release context.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn GitHub issues into a structured implementation plan?▼

To turn GitHub issues into an implementation plan, provide the issue number to fetch details via GitHub CLI and align them with repository context. This generates a conversation-only plan covering scope, constraints, files to change, and an effort estimate.

What is scope validation for non-trivial feature work?▼

Scope validation for non-trivial feature work is checking MVP boundaries, architecture decisions, and security constraints before implementation. It explicitly marks missing information and required decisions to prevent costly implementation churn.

How do I create an actionable implementation approach before coding starts?▼

You create an actionable implementation approach by reading project memory files and aligning the request with repository constraints. This produces a plan detailing the approach by layer, files to change, and an effort estimate without writing any files.

Can I use GitHub CLI to fetch issue details for planning?▼

Yes, you can use GitHub CLI to fetch issue details for planning. The skill optionally retrieves specific GitHub issues by number and uses the linked context to avoid mis-scoping during the implementation plan generation.

When should I not use automated implementation planning?▼

You should not use automated implementation planning for trivial tasks that do not require scope validation, architecture checks, or security boundary reviews. It is specifically designed for non-trivial feature work where unknowns and required decisions must be explicitly identified.