debug-specs

Diagnose application bugs by reviewing and adjusting specification files.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill debug-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-specs
Source: https://github.com/Codeplain-ai/onboarding-flow/tree/main/.claude/skills/debug-specs
Command: npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill debug-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you identify and resolve bugs in a running application by meticulously reviewing the specifications, analyzing the generated code, and making necessary adjustments.

Core Features & Use Cases

  • Bug Diagnosis: Identifies the root cause of unexpected behavior, visual glitches, crashes, or incorrect logic in the app.
  • Spec Review: Provides guidelines on reviewing .plain files and imported specifications.
  • Code Tracing: Guides you in tracing the issue from the generated code back to the specs.
  • Spec Modification: Recommends and executes changes to specifications based on the root cause.
  • Verification: Assists in verifying and reporting the fix to the user.
  • Use Case: If you notice that the application's buttons are not working as expected, use this Skill to trace the issue, review the relevant specs, and make necessary changes.

Quick Start

Use the debug-specs skill to trace the issue related to module 'button-component'.

Frequently Asked Questions about debug-specs

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

FAQPage Schema
How do I diagnose bugs by reviewing application specifications?

To diagnose bugs by reviewing application specifications, trace unexpected behavior from generated code back to the spec files, identify conflicts or ambiguity, and adjust the specifications to resolve the incorrect logic.

What is the best way to fix incorrect application behavior traced to spec files?

The best way to fix incorrect application behavior traced to spec files is to analyze the generated code, pinpoint the root cause within the specifications, modify the conflicting specs, and verify the application fix.

How do I trace a visual glitch or crash back to its root cause in functional specifications?

To trace a visual glitch or crash back to its root cause in functional specifications, meticulously review the generated code, identify the exact mismatch with the intended behavior, and update the relevant specification files.

Can I resolve conflicts or ambiguity in plain files without modifying the source code directly?

Yes, you can resolve conflicts or ambiguity in plain files by adjusting the specifications themselves, which corrects the generated application code and fixes the unexpected behavior without direct manual source code edits.

When should I use specification adjustment instead of direct code patching for application debugging?

You should use specification adjustment instead of direct code patching when the application debugging process reveals that the root cause of the unexpected behavior stems from conflicts, ambiguity, or incorrect logic in the functional specs.