forge-troubleshoot

Diagnoses Plan Forge failures including runs, environments, and code errors via MCP server.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/srnichols/plan-forge --skill forge-troubleshoot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-troubleshoot
Source: https://github.com/srnichols/plan-forge/tree/main/presets/shared/skills/forge-troubleshoot
Command: npx skills add https://github.com/srnichols/plan-forge --skill forge-troubleshoot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires forge_smith, forge_validate, forge_sweep, forge_plan_status, forge_diagnose, forge_cost_report, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The forge-troubleshoot skill addresses issues with Plan Forge, including failed runs, broken validation gates, misconfigured environments, and other errors.

Core Features & Use Cases

  • Issue Diagnostics: Identify the root cause of various Plan Forge problems.
  • Environmental Checks: Scan for missing tools, incorrect settings, and connection issues.
  • Setup Validation: Ensure all necessary Plan Forge files are present and correctly configured.
  • Run Status Check: Retrieve and analyze the latest run report for failures or errors.
  • Code Quality Scan: Detect issues that may block code validation gates.

Quick Start

Use the forge-troubleshoot skill to diagnose the error: 'forge_troubleshoot "Slice 3 failed"'

Frequently Asked Questions about forge-troubleshoot

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

FAQPage Schema
How do I troubleshoot a failed Plan Forge run?

To troubleshoot a failed Plan Forge run, you can diagnose the error by running the forge-troubleshoot tool with the specific failure message, such as 'Slice 3 failed'. It retrieves and analyzes the latest run report to identify the root cause of the failure.

Why does Plan Forge validation keep failing?

Plan Forge validation may fail due to code quality issues that block validation gates. The troubleshooter scans your code to detect these blocking issues and checks that all necessary Plan Forge files are present and correctly configured.

How do I check for missing tools in my Plan Forge environment?

To check for missing tools in your Plan Forge environment, perform an environmental check. This process scans for incorrect settings, missing tools, and connection issues with the MCP server to ensure your setup is fully configured.

What is the best way to resolve Plan Forge environment configuration errors?

The best way to resolve Plan Forge environment configuration errors is to use an automated diagnostics skill. It identifies misconfigured environments by interacting with Plan Forge tools and the MCP server to suggest targeted solutions.

Do I need the MCP server to diagnose Plan Forge issues?

Yes, you need the MCP server to diagnose Plan Forge issues. The troubleshooting process requires interaction with Plan Forge tools and the MCP server to accurately identify and suggest solutions for environment and code errors.