forge-shape

Creates and refines GitHub issues with acceptance criteria, milestones, and spec decomposition.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague ideas or approved specs into well-scoped, trackable GitHub issues is time-consuming and error-prone. This Skill structures issue creation, refinement, backlog organization, and spec-to-issue decomposition so every work item has clear scope, testable acceptance criteria, and proper dependency wiring. ## Core Features & Use Cases - Issue Shaping: Create new issues or refine existing ones with action-oriented titles, acceptance criteria, scope boundaries, labels, and milestones via the GitHub CLI. - Spec Decomposition (--from-spec): Parse an approved spec file, identify vertical slices, and generate a parent spec issue plus sub-issues with blocked-by relationships and project board fields. - Backlog & Milestone Organization: Assess milestone groups for scope clarity, dependency completeness, and ordering, then propose restructuring. - Use Case: After a design spec is approved, run the skill with --from-spec to automatically produce a tracked spec issue and a set of independent, testable sub-issues linked to the milestone. ## Quick Start Ask the assistant to decompose the approved spec at docs/specs/my-feature.md into GitHub issues using forge-shape.

Frequently Asked Questions about forge-shape

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

FAQPage Schema
How do I break a spec document into GitHub issues?

Run the skill with --from-spec followed by the spec file path. It validates the spec's required sections, proposes vertical slices with acceptance criteria, and creates a parent spec issue plus linked sub-issues after approval.

How do I refine a vague GitHub issue with acceptance criteria?

Invoke the skill in standard mode and reference the issue number. It reads the issue via gh issue view, identifies gaps like missing acceptance criteria or labels, and proposes concrete improvements for your approval.

Does the spec decomposition mode require manual approval?

In supervised mode it waits for user approval before creating issues. In autonomous mode (CLAUDE_MODE=autonomous), --from-spec decompositions are auto-approved, but interactive shaping always requires human approval.

Can it add issues to a GitHub Projects board?

Yes, if the project board is enabled in .forge/config.yaml. It uses GraphQL mutations to add items and set Track and Lane fields, and skips this step silently when the board is not configured.

What are the limitations of automated spec decomposition?

It halts on specs already marked Implemented and warns on Draft status. It does not make architecture decisions or implement code, and dependency wiring relies on GitHub's native blocked-by relationships.