forge:plan

Transform feature requests into structured plans with steps, gates, and reviewer roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The FORGE plan pipeline translates vague feature requests into a concrete, auditable plan with steps, gates, and reviewer roles, increasing visibility and control over feature development.

Core Features & Use Cases

  • Structured planning: Converts user input into a plan document with milestones, tasks, and gates.
  • Gate-driven execution: Automates review and approvals at key transitions to ensure quality and alignment.
  • Documentation generation: Produces plan artifacts (docs/PLAN.md) for project onboarding and tracking.

Quick Start

Describe the feature you want to plan, then run /forge:plan to start the planning pipeline.

Frequently Asked Questions about forge:plan

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

FAQPage Schema
How do I turn a vague feature request into an actionable plan with review gates?

To turn a vague feature request into an actionable plan, describe the feature and run the planning pipeline to generate structured milestones, tasks, and gates for auditable execution.

What is gate-driven execution in feature planning?

Gate-driven execution in feature planning is a mechanism that automates review and approvals at key transitions to ensure quality and alignment before moving to the next milestone.

How do I prepare documentation for project onboarding and tracking?

To prepare documentation for project onboarding, use a structured planning pipeline to transform requirements into a plan artifact, producing a centralized document for tracking.

Does this feature planning approach work without external dependencies?

Yes, this feature planning approach works without external dependencies, running a standalone pipeline to orchestrate brainstorming, mode assessment, and gate-based approvals independently.

What is the best way to structure milestones and reviewer roles for a new feature?

The best way to structure milestones and reviewer roles is to use an orchestrated planning pipeline that automatically maps feature requirements to defined reviewer roles and gates.