forge-plan

Convert research documents into structured implementation plans with Beads issue tracking.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill forge-plan-jupes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-plan
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/forge-plan
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill forge-plan-jupes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates the planning phase of the Forge pipeline, transforming research documents into actionable implementation plans. It streamlines the transition from research to development by integrating Beads issue tracking and Test-Driven Development (TDD) principles.

Core Features & Use Cases

  • Research to Plan Conversion: Transforms research documents into detailed implementation plans.
  • Beads Issue Integration: Automates the creation of Beads issues for task tracking and dependency management.
  • TDD Strategy Implementation: Sets up a TDD-based test strategy for feature development.
  • Use Case: When you have a research document ready and need to create a structured plan for feature development, using /forge-plan <slug> or /forgemaster will guide you through the process.

Quick Start

Run the /forge-plan <slug> command to start the planning process for your feature.

Frequently Asked Questions about forge-plan

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

FAQPage Schema
How do I convert a research document into a TDD implementation plan?

You can convert research documents into a TDD implementation plan by running the `/forge-plan <slug>` command, which structures feature development and establishes a test-driven strategy.

What is the best way to integrate Beads issue tracking into development planning?

Integrating Beads issue tracking into development planning is handled automatically during the plan conversion process, which creates tracked issues and manages feature development dependencies.

How does TDD test strategy work during feature development planning?

TDD test strategy during feature planning works by enforcing Test-Driven Development practices within the generated implementation plan, ensuring development tasks are structured around test outcomes.

Do I need a completed research document before starting pipeline orchestration?

Yes, you need a completed research document before starting pipeline orchestration, because the planning phase specifically transforms existing research outcomes into actionable implementation plans.

Can I use this for coordinating development efforts across multiple features?

Yes, you can use this for coordinating development efforts across multiple features by running the `/forgemaster` command, which guides task management and dependency tracking via Beads issue integration.

What are the limitations of using Beads issues for TDD pipeline orchestration?

A limitation of using Beads issues for TDD pipeline orchestration is that the Skill is strictly designed for the planning phase, meaning it does not handle downstream execution or testing automation.