forge-plan

Generates implementation plans for GitHub issues using writing-plans methodology with codebase exploration.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-plan-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-plan
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-plan
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-plan-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved GitHub issue into a concrete, reviewable implementation plan requires gathering issue context, assessments, specs, and codebase knowledge manually. This Skill automates that planning ritual and enforces human approval before any code is written. ## Core Features & Use Cases - Full planning mode: Assembles context from the GitHub issue, prior assessment comments, linked spec files, and a scoped codebase explorer agent, then invokes the writing-plans methodology to produce a detailed TDD-oriented implementation plan. - Lite mode: Uses native Claude Code plan mode for lightweight planning, posting the plan to the issue via a hook. - Approval gate and execution handoff: Posts the plan to the GitHub issue, blocks on explicit human approval, then dispatches execution via subagent-driven, inline, or manual strategies. - Use Case: After /forge-assess approves issue #42, run the skill to produce a plan saved to tmp/issue-delivery/42/implementation-plan.md, posted to the issue, and executed on a fresh feature branch. ## Quick Start Run /forge-plan 42 to generate a full implementation plan for GitHub issue 42 and post it for approval.

Frequently Asked Questions about forge-plan

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

FAQPage Schema
How do I create an implementation plan for a GitHub issue?

Run /forge-plan with the issue number, for example /forge-plan 42. The skill fetches the issue, any assessment comment, and linked spec, explores the codebase, and writes a plan to tmp/issue-delivery/<number>/implementation-plan.md, then posts it to the issue.

What is the difference between full mode and --lite mode?

Full mode uses the writing-plans methodology with a multi-source context package and produces a detailed TDD plan. Lite mode uses native Claude Code plan mode for a lightweight high-level plan posted to the issue via a hook.

Does forge-plan require a prior assessment before planning?

No. An assessment comment from /forge-assess is recommended but not required. If none is found, the skill warns and proceeds, skipping the risk cross-check step in Phase 3.

What happens if the writing-plans skill invocation fails?

The skill announces that full planning is unavailable and falls back to the lite mode procedure, which uses native plan mode to produce and post a lightweight plan instead.

Can I control how the approved plan gets executed?

Yes. Pass --execute=subagent, inline, or manual to override the default strategy. Without it, the strategy is chosen from CLAUDE_MODE and the plan's task dependency structure, or you are prompted in supervised mode.