vocion/vocion-core/read-the-ask-whole
Claude Code and agent skill by vocion/vocion-core
- community
Checking that the SKILL.md file is still in the repository.
What the engineer reads before changing a file: the contract first and in full, then the issue the client filed and its comments, then the thread the ask came from. What counts as a contract conflict, and that a conflict is an ask filed, never a guess made. Read at the start of every engineering task whose request carries an issue URL or a thread permalink.
Install
npx vskill@latest install vocion/vocion-core/read-the-ask-wholeSKILL.md
The same SKILL.md was published earlier as vocion/vocion-core/read-the-ask-whole.
Reading the ask whole before the first edit
The contract is the only thing you are bound to. The issue and the thread are where the contract came from, and they say the things a contract leaves out: the example that broke, the field name the client uses, the screen they were on. Read them to build the right thing inside the contract, never to widen it.
In this order
- The contract, in full:
objective,allowedPaths,acceptanceContract,
requiredChecks, baseSha, riskClass, requestSummary. This is what QA judges you against and what the person approved.
- The issue, when the request's evidence carries one:
tracker_read_issue with its key. The description and the comments in order, the attachments that show the data or the screen. Note the reporter's exact words for the thing that is wrong.
- The thread, when the request came from chat:
chat_read_threadwith
the permalink. The follow-ups narrow the ask; a reply often names the one case that matters.
- The pull request's own checks, after the first push:
repo_read_check_logs
on your pull request before you report, so the report says what is red and why in your own words, not the engineer's hope.
What a conflict is
The issue or the thread says something the contract does not allow for:
- the fix needs a file outside
allowedPaths; - an acceptance criterion contradicts what the reporter described;
- the example the client gave does not reproduce on
baseSha; - the thread settled on a different outcome than the contract's objective.
A conflict is an ask, not a guess. File it (file_ask) with the contract line, the issue or thread line that contradicts it, and the two ways it could be resolved; mark the task's assumptions with what you did meanwhile if the rest of the work can go on. Never widen allowedPaths yourself, never satisfy the thread instead of the contract, never "fix it properly" beyond what was asked. The contract is a person's decision.
What you do not do with what you read
No reply in the thread, no comment on the issue, no status change on the board. The PM owns every word the client reads. Your words go on the pull request (report-on-the-pull), where the reviewer and the person who merges read them.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingpackages/core/templates/plugins/software-factory/skills/read-the-ask-whole/SKILL.md
Popularity
- Repository stars
- 2
- Repository forks
- 1
- 7-day trend score
- 10
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/vocion/vocion-core/read-the-ask-whole)