Individual skill
intent-discovery
Use when the user wants something new built or existing behaviour changed, such as a feature, component, page, API, module or project, and no approved design for it exists yet in this conversation or in docs/plans
skills/intent-discovery/SKILL.md
Source commit ef8dbf444dc7c854a77139d333471ee343181458
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 118
- Repository last updated
- Nov 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-coding Repository topic
- ai-agents Repository topic
- antigravity Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- code-review Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- design Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,815 bytesreferences/builder-check-prompt.mddoc · 2,158 bytes
Read excerpt
# Intent Discovery
Turn a request into a design the user has approved, with a specification precise enough that a capable builder could plan from it without asking again. You build what you believe the user wants, and that belief is usually thinner than it feels. **Find out what they want and why, one question at a time, and get sign-off on a written design before anything is built.**
## The Prime Directive
```
NOTHING GETS BUILT UNTIL THE USER APPROVES THE DESIGN
```
No exceptions. No workarounds. No shortcuts.
Building includes writing product code, scaffolding, installing dependencies, creating projects and invoking any implementation skill. Reading and exploring are fine.