Intent Debugger skill
A skill that turns a vague idea into a structured requirements list and asks precise questions until you confirm understanding
- 124 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill only runs a dialogue about requirements: it runs nothing, changes no files and makes no network calls.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/intent-debuggerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill only runs a dialogue about requirements: it runs nothing, changes no files and makes no network calls.
This is third-party code. Review the repository files before installing.
What it does
Intent Debugger helps check whether an agent understood the task before design and code begin. You describe the desired outcome, usage, concerns and examples in plain words, and the skill returns three blocks: a requirements breakdown (goal, scenarios, functions, flow, constraints), questions explaining why each matters, and a current agreement marking confirmed and tentative items. Each question is worded so it can be answered directly and so the answer changes the requirements. The loop repeats until you confirm the understanding is right, and after that the skill plans, designs and implements nothing by itself. There is a Codex version, a Claude Code adapter and a way to use the file as a DeepSeek system message.
Who it is for. Product managers and developers who describe an idea loosely and want to see whether it was understood correctly before an agent starts on a plan or code.
Good fit when
- You have an idea but no professional terms for it and the description comes out roundabout.
- The agent understood the request differently from you and last time the work had to be redone.
- A client sent contradictory wishes and they must be merged into a checkable list.
- Before Plan mode you first need agreement on what exactly is being built and where the limits lie.
Not a fit when
- Requirements are already clear and you need an implementation plan: Plan mode serves that.
- You need a technical design or code: the skill stops before that.
- You want an automatic move to implementation after agreement.
Example request
Use intent-debugger: I want to build a tool that helps a team quickly find the right materials. Ask clarifying questions.Limitations
The skill stays at the requirements level: planning, design and implementation do not start, even after confirmation. All three platforms use the same SKILL.md file, and the author notes the adapters describe how to load it and do not mean an equally tested effect in every client version. The DeepSeek API has no file-based skill discovery, so the file text goes in as the first system message. The main README is in Chinese and the English version is in `README_EN.md`. The latest commit is from November 2026.
How to disable. Delete the `intent-debugger` folder from the skills directory: `~/.claude/skills/` or `.claude/skills/` for Claude Code, `$CODEX_HOME/skills/` for Codex. Reload the agent.
FAQ
How does the skill differ from Plan mode?
Intent Debugger answers what exactly to build, why and where the limits lie. Plan answers how to implement already confirmed requirements in a specific project. They can be used independently.
How do I install it in Claude Code?
Copy `skill/intent-debugger` into `~/.claude/skills/intent-debugger/` or the project's `.claude/skills/`, then call `/intent-debugger`.
Can I download an archive?
Yes, the release holds an `intent-debugger-skill.zip` file. Unpacking gives an `intent-debugger` folder to place in the skills directory.
What does the skill return each round?
Three blocks: a requirements breakdown, questions explaining why they matter and a current agreement marking confirmed and tentative points.
Does it work with DeepSeek?
Yes, through a system message: the full text of SKILL.md goes in as the first message, followed by your idea.
Discussion
No questions or reviews yet.
Related
SkillsA skill that cross-examines a plan before work starts: numbered questions in rounds with a recommended answer and no changes until you confirm
A dialogue skill that helps work out why a task stalled, find hidden assumptions and choose a single next step.
Deep Research Skills
Deep Research Skill
A structured deep-research skill for Claude Code, OpenCode and Codex with human control at every step
Skill silently rewrites your request for the model family that answers it, then answers without showing the rewrite.
A tutoring skill for STEM and AI: it finds the knowledge gap first, then teaches one step and checks understanding
A skill that analyzes materials and subtitles, checks facts against sources and keeps a personal library in a local folder.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Intent Debugger (this card) | no | 124 | |
| Awesome Requirements Writer | no | 105 | writes a requirements document; Intent Debugger asks questions until you confirm understanding |
| grill-with-ui | no | 330 | grills a UI plan; Intent Debugger clarifies goal, scenarios and limits before design |
README in short
The README covers three platforms, example dialogues, a comparison with Plan mode and contribution rules. The download counter in the header adds clones and archive downloads and does not equal active users.