forge-assess

Generates pre-implementation assessments for GitHub issues with fit checks, risks, and approval gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding a GitHub issue without validating scope, risks, or alignment with an existing spec, leading to rework and regressions. This Skill enforces a structured pre-implementation assessment gate before any code is written. ## Core Features & Use Cases - Structured Assessment Template: Produces a fit check, key risks with severity ratings, alternative approaches, a PROCEED/REVISE/DEFER recommendation, and a value rating for any issue. - Spec Conformance Mode: Detects a Spec: link in the issue body and runs a lighter conformance check against the spec file instead of the full assessment. - Automated Issue Posting & Approval Gate: Writes the assessment to tmp/issue-delivery/<number>/assessment.md so a hook posts it as an issue comment, then applies an autonomous or human approval gate before planning. - Use Case: A developer is asked to implement issue #42. The Skill fetches the issue, evaluates scope and risks, posts the assessment as a comment, and only proceeds to /forge-plan after approval. ## Quick Start Run the forge-assess skill on issue 42 to produce and post a pre-implementation assessment before any coding begins.

Frequently Asked Questions about forge-assess

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

FAQPage Schema
How do I run a pre-implementation assessment on a GitHub issue?

Invoke the skill with the issue number before writing any code. It fetches the issue body with gh issue view, checks for a linked spec, produces a fit check, risk list, alternatives, and recommendation, then posts the result as an issue comment.

What is a spec conformance check for GitHub issues?

A spec conformance check is a lighter assessment used when the issue body contains a Spec: path line. The skill reads the spec file and verifies the issue scope matches the spec's decomposition and architecture decisions, returning SPEC-ALIGNED or DRIFT DETECTED.

Can the assessment auto-approve without human review?

Yes, when CLAUDE_MODE is autonomous and all guardrails pass: fit check CLEAR, recommendation PROCEED, no high risks, no ADR boundary overlap, and spec conformance SPEC-ALIGNED. Otherwise it halts and waits for explicit human approval.

How is the assessment posted to the GitHub issue?

The skill writes the assessment to tmp/issue-delivery/<number>/assessment.md using the Write tool. A PostToolUse hook detects that path and automatically posts the content as a comment on the linked issue.

When should I not proceed after an assessment?

Do not proceed when the fit check is UNCLEAR, any risk is rated high, the recommendation is REVISE or DEFER, the story touches ADR-governed boundaries, or spec drift is detected. These cases require human review and possible revision.