forge

Generates structured multi-phase planning documents with decision forks for GitHub Issues or docs.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill forge-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/forge
Command: npx skills add https://github.com/Claudfather/clauDNA --skill forge-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-PR workstreams often start with vague plans that create false alignment, drift from the actual codebase, and collapse under review. Forge produces a rigorous, ratifiable planning document with explicit decision forks, sized phases, and verified evidence so teams can coordinate before implementation begins. ## Core Features & Use Cases - Structured Plan Authoring: Emits plans in a shared publishable-doc contract with Summary, Evidence, Implementation Plan, Test Plan, and Verification Checklist sections, plus Decision Forks, Risks, and Sequencing tables. - Decision Fork Management: Catalogs architecture forks with options, trade-offs, a recommended lean, a designated ratifier, and lock/reopen tracking via [FORK-LOCK] issue comments. - Multi-Phase Publishing: Splits large initiatives into an epic plus per-phase documents, publishing them as cross-linked GitHub Issues or a PR-reviewable docs directory. - Use Case: Before starting a three-month migration spanning five PRs, run forge on the topic to produce an epic issue with sized phases, locked decision forks, and a verification checklist, then hand it to the ironclad hardening loop for multi-lens review. ## Quick Start Ask the AI to forge a plan for your multi-phase initiative, optionally passing a topic or issue URL and an output target such as github or docs.

Frequently Asked Questions about forge

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

FAQPage Schema
How do I create a technical plan for a multi-PR project?

Invoke forge with a topic description or issue URL. It researches the codebase, identifies decision forks and risks, then drafts a structured plan with sized phases that can be published as a GitHub Issue epic plus per-phase issues.

When should I use forge instead of plain plan mode?

Use forge when the work is multi-phase, multi-person, decision-heavy, or high-stakes. For single-PR changes with an obvious path, plain plan mode or a lighter scoping skill is the better choice; forge's right-size gate flags marginal cases.

Can forge publish a plan as GitHub Issues?

Yes. With the github output flag, forge hands its plan documents to the shared publish skill, creating an epic issue first, then per-phase issues in order, and cross-linking them with a phase table on the epic.

What are decision forks in a project plan?

Decision forks are documented points where multiple viable approaches exist and reasonable people disagree. Each fork lists options with trade-offs, a recommended lean, a designated ratifier, and a status that is locked via a fork-lock comment.

Does forge run code reviews on the plan it writes?

No. Forge runs only a structural pre-flight check covering skeleton completeness, evidence verification, fork formatting, and phase sizing. Deeper multi-lens review is delegated to the ironclad hardening loop after publication.