forge-force-advancelisted

Override a blocking gate and advance the pipeline stage, recording a lesson with the user's stated reason. Use this skill ONLY when a user explicitly asks to "force advance", "skip the gate", "override the blocker", "advance anyway", or otherwise expresses intent to proceed despite failing gate criteria. Make sure to require an explicit `--reason` justification from the user (≥ 10 characters) before invoking the script — the lesson recorded becomes part of the retrospective and protects future-them from forgetting why this happened. Do NOT use this skill proactively or as a workaround for fixable gate failures; if the user hasn't asked to override, ask whether they want to fix the blocker first.
tonmoy007/forge-plugins · ★ 1 · AI & Automation · score 72

Install: claude install-skill tonmoy007/forge-plugins

# Forge Force Advance Bypasses the gate-blocker check, advances `pipeline/state.md` by one stage, and records a permanent lesson with the user's reason. The overridden gate criteria themselves remain failed — they'll show up again in subsequent gate checks unless actually resolved. This is a **conscious admission** that work was incomplete at advance time. The lesson is the only protection against that fact being forgotten. ## When to Use - User says `/forge:force-advance` - User says "force advance", "skip the gate", "advance anyway", "override the blocker" - User has acknowledged they cannot or will not resolve a blocker right now (e.g., needs ops help, blocked on a third party, deliberately deferring scope) - User has already heard `/forge:why` output and decided to proceed anyway ## When NOT to Use - The user is asking *how* to fix a blocker — explain or run `/forge:why` instead - The blocker is trivially fixable (missing file, missing section heading) — fix it - The user hasn't asked to override — never proactively suggest force-advance as a workaround; gates exist for a reason ## Steps 1. If the user hasn't provided a reason yet, ask: "Force-advance records a permanent lesson. What's the reason you're advancing despite the active blockers? (≥ 10 characters; this will be reviewed in retro.)" 2. Wait for the user's reason. Confirm it's at least 10 non-whitespace characters. 3. (Optional but recommended) Run `/forge:why` first to surface the actual blocke