From forge
Check gate conditions for the current phase and advance to the next phase if all pass. User-invoked only: do not auto-trigger.
How this skill is triggered — by the user, by Claude, or both
Slash command
/forge:advanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Evaluate all exit gate conditions for the current phase. If every gate passes, update `forge-state.json` to the next phase and invoke the next phase's skill. If any gate fails, report which gates failed and what evidence is missing. User-invoked only: phase advancement is an earned progression and must never be AI-triggered.
Evaluate all exit gate conditions for the current phase. If every gate passes, update forge-state.json to the next phase and invoke the next phase's skill. If any gate fails, report which gates failed and what evidence is missing. User-invoked only: phase advancement is an earned progression and must never be AI-triggered.
Never fabricate or infer evidence that is not on disk. "The tests probably pass" is not evidence. The .forge/evidence/verification/ directory is the source of truth.
/forge:advance
.forge/forge-state.json. If no active workflow, report "No active Forge workflow" and exit..forge/evidence/verification/ and workflow state fields. Record PASS or FAIL per gate.forge-state.json unchanged.
b. Report every failing gate with the specific missing evidence.
c. Suggest which skill the user should run to produce the missing evidence.
d. Exit.phases_completed.
b. Set current_phase to the next phase in the sequence.
c. Update last_session to now.
d. Write the updated state.
e. Invoke the next phase's skill.discovery → design → planning → execution → verification → integration → (complete)
.forge/forge-state.json mutated only on successful advance.npx claudepluginhub caseyrtalbot/forge --plugin forgeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.