skills.rest
FS-GG
FS-GGOFFICIAL
Explore all skills by this author →
GitHub

fs-gg-sdd-troubleshooting

Diagnose blocking issues in the FS.GG SDD lifecycle using summary counters.

Updated Jul 6, 2026
Search Tags:#diagnosis#issue resolution#sdd lifecycle#fs-gg-sdd#summary counters
One-click install
npx skills add https://github.com/FS-GG/FS.GG.Game --skill fs-gg-sdd-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fs-gg-sdd-troubleshooting
Source: https://github.com/FS-GG/FS.GG.Game/tree/main/.agents/skills/fs-gg-sdd-troubleshooting
Command: npx skills add https://github.com/FS-GG/FS.GG.Game --skill fs-gg-sdd-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identifies and resolves blocking issues in the FS.GG SDD lifecycle that prevent progression by analyzing summary counters and providing actionable next steps.

Core Features & Use Cases

  • Diagnosis: Analyzes the SDD lifecycle stages that are blocked or reporting 'noChange'.
  • Summary Counters: Provides a clear, readable summary of the issue (e.g., blocking ambiguities, checklist failures).
  • Quick Fix Instructions: Offers a straightforward guide on resolving issues based on the summary counters.
  • Use Case: If the 'clarify' stage in the SDD lifecycle is not advancing, this skill helps identify if there are unresolved ambiguities or checklist failures that need attention.

Quick Start

Use the 'fs-gg-sdd troubleshoot' command with the '--text' option to get detailed diagnostic information.

Frequently Asked Questions about fs-gg-sdd-troubleshooting

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

FAQPage Schema
How do I diagnose blocking issues in the SDD lifecycle?▼

Diagnose SDD lifecycle blockages by running the 'fs-gg-sdd troubleshoot' command with the '--text' flag to output detailed diagnostic information. This analyzes summary counters to pinpoint stages that are blocked or reporting noChange, identifying unresolved ambiguities or checklist failures.

Why does the clarify stage in the SDD lifecycle report noChange?▼

The clarify stage reports noChange due to unresolved ambiguities or checklist failures preventing progression. Troubleshooting tools analyze summary counters to identify these specific blocking conditions and provide actionable next steps to resolve the blockage.

What is the best way to resolve checklist failures blocking the SDD lifecycle?▼

Resolve checklist failures by analyzing summary counters to locate the exact failure point. The troubleshooting process provides quick fix instructions and a straightforward guide detailing the actionable steps required to clear the blockage and resume the lifecycle.

Can I get detailed diagnostic output for SDD lifecycle stages?▼

Detailed diagnostic output for SDD lifecycle stages is generated by executing the troubleshoot command with the '--text' flag. This provides a clear, readable summary of blocking issues, enabling you to identify the cause and apply the recommended fixes.

Do I need specific flags to identify blocking ambiguities in the SDD lifecycle?▼

Specific flags are required to identify blocking ambiguities; you must use the '--text' option with the troubleshoot command. This generates the detailed output necessary to read the summary counters and accurately diagnose the cause of the blockage.

Related Skills

Explore More Software Engineering Skills→
FS-GGFS-GG

check-board

Reconcile the FS-GG Coordination Projects board with GitHub issue states.

Official
Advanced
nk10nikhilnk10nikhil

hive-test

Run iterative agent tests with checkpoint resume and failure analysis.

Community
Advanced
rajnishkhatrirajnishkhatri

sdd-implement

Execute SDD Stage 6 tasks using red/green TDD and EARS verification.

Community
Advanced
guillempucheguillempuche
6

playwright-devops

Collect and group failed GitHub Actions logs for Playwright CI commits.

Community
Intermediate