clarify
Skill0 starsChanged 7 days agoMITView on GitHub
Use at intake before the charter, or when a developer asks to pin down a ticket's details - scans the ticket against ten categories, infers every open point with a recommended answer and records each inference (asks only when the user opted in or a hard-to-undo point needs a human).
81 other projects use a version of this.
Adopted by
Most recently taken up by
- RichardDow/skillstheir own version, first seen Nov 15, 2026
- ZaxbyHub/opencode-swarmtheir own version, first seen Nov 15, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- mel0nyrame/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use quieter, arrange and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HK-hubSkillquieter
Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.
Also in 29 projects that use this
HK-hubSkillarrange
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 14 projects that use this
zwy123zwySkillnormalize
将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。
Also in 19 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
- +8 more from HK-hub
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- spool-lab/spool★ 592same name
- paperboytm/spool★ 590same name
- talesofai/cohub★ 585same name
- ZaxbyHub/opencode-swarm★ 531same name
- zaxbysauce/opencode-swarm★ 519same name
- educlopez/ui-craft★ 441same name
- nexmoe/DayBee★ 424same name
- nexmoe/eve★ 424same name
- ryanthedev/code-foundations★ 381same name
- Southclaws/storyden★ 348same name
71 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/work/platforms/claude.mdCLAUDE.md
- llms.txtllms.txt
- consistencySkill
- debuggingSkill
- documentationSkill
- featureSkill
- hexagonalSkill
- initSkill
- jobs-and-state-machinesSkill
- lang-clojureSkill
- lang-cppSkill
- lang-csharpSkill
- lang-elixirSkill
- lang-erlangSkill
- lang-goSkill
- lang-javaSkill
- lang-kotlinSkill
- lang-phpSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-scalaSkill
- lang-swiftSkill
- lang-typescriptSkill
- memorySkill
- parallel-workSkill
- performanceSkill
- qualitySkill
- reportSkill
- review-integrationSkill
- statusSkill
- testingSkill
- workSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 78 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read-only repo facts: grep and ranged reads of the code the ticket names.
- Very specific: line 24
Do not read whole files. Do not start research here.
- Very specific: line 48
Ask: when loops run checkpoint intake prints ask (the user put intake in their checkpoints), or when the user asked in this request ("ask …
- Very specific: line 62
Record: Write <run dir>/clarifications.md.
- Very specific: line 72
Play back: Before the charter is written, give the user one short paragraph: the reading the run will follow and the inferred items they …
- Distinctive: line 76
Never ask a question that would not change an acceptance criterion, the plan or a test.
- Distinctive: line 77
Never ask more than 5 questions in one session.
- Very specific: line 78
Stop when every category is Clear, or its open points are recorded.
- Very specific: line 79
Do not edit ticket.md. The ticket is the user's text.
“Common” is measured: kept by at least 6 in 10 of the 78 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clarify
Adapted from GitHub Spec Kit's /speckit.clarify (MIT, https://github.com/github/spec-kit, templates/commands/clarify.md); play-back idea from obra/superpowers brainstorming (MIT). Original wording; no Spec Kit prose is copied.
The goal: a developer should be able to pin down every detail of a ticket before code is written. The skill finds the gaps, closes them with the recommended answer, and writes each one down so it can be reviewed or reversed later. Nobody is interrupted unless the user opted in or undoing an inference later would be hard.
When
- At intake, after the ticket is fetched and before the charter is written (WORKFLOW §2.0). The lead runs it; role agents do not.
- Outside a run, when a developer asks to clarify a ticket or text. Then the output is the list only (step 7).
- Standalone:
/loops:clarify <ticket ref or text>with no run infers and prints the list. Add--askto be asked the open points instead (step 4). Inside a run, the mode follows the intake checkpoint.
Inputs
<run dir>/ticket.md(the normalised ticket). Get the path withloops run dir.<run dir>/research/memory.md, when it exists (ai-memory briefing,loops:memory).- Read-only repo facts: grep and ranged reads of the code the ticket names. Cite
path:line.
Do not read whole files. Do not start research here; research/code.md and research/practices.md are other phases' work.
Procedure
- Scan ten categories. For each, mark the ticket
Clear,PartialorMissing:- scope: what is in and out;
- data model: entities, fields, identifiers, persisted shape;
- user or CLI flow: who triggers what, and what they see back;
- non-functional: performance, security, observability, limits;
- integrations: external APIs, brokers, files, other packages;
- edge and failure cases: empty, duplicate, concurrent, partial failure;
- constraints and trade-offs: compatibility, deadlines, rules the repo already sets;
- terminology: names the ticket uses that the code or docs define differently;
- completion signals: how the user will know it is done;
- placeholders: TBD, "etc.", unnamed options.
- Keep only points that matter. A
PartialorMissingpoint is recorded only if the answer would change an acceptance criterion, the plan or a test. Drop the rest without writing them down. - Build each item. For each kept point, write:
- the question, and the recommended answer (the narrowest reading that meets the stated goal). Give 2-4 alternatives when the choice is real;
- its source: a ticket line, a
path:line, or a named project convention; - its reversibility:
easyorhard(the hard list is in step 5).
- Choose the mode.
- Ask when
loops run checkpoint intakeprintsask(the user putintakein their checkpoints), or when the user asked in this request ("ask me",--ask). Ask at most 5 questions, one at a time, each with its recommended answer first. "yes" accepts the recommendation. - Infer otherwise. Inferring means accepting the recommended answer and recording it as
inferred. This is the default: no question is asked. Open points beyond the 5-question cap are inferred and recorded like the rest, so no detail is left unrecorded.
- Ask when
Hard-to-undo points. A point is
hardwhen the answer is one of:- a public API, a CLI name or flag;
- a persisted schema, an event field, a migration;
- deleting data or files;
- an external side effect (publish, push, send, pay);
- security, auth or permission posture;
- a licence or a new dependency;
- anything that moves the scope's edges.
In Ask mode, a hard item is asked like any other. In Infer mode, a hard item is still asked when the lead is talking to a user who can answer now, because undoing the inference later would be costly. When no user can answer (a headless run), take the most reversible option and record it
inferred · hard. Decisions show in the report and the PR (WORKFLOW §2.7).Record. Write
<run dir>/clarifications.md. Start each session with## Session <YYYY-MM-DD>(today's date, from the run). One line per item:K<n> [category] Q: <question> → A: <answer> (inferred|asked · easy|hard · <source>)- Numbering
K1, K2, ...is per run and never reused. - Each inferred answer becomes a charter Assumption
A<n>that cites its item (A1: … (K3)), and is logged withloops run decide --topic assumption --note "K<n>: <answer>" --ref clarifications.md. - Each asked answer is logged with
--by useras well:loops run decide --by user --topic assumption --note "K<n>: <answer>" --ref clarifications.md.
- Numbering
- Outside a run. Print the list in the reply, in the same line format. Write a file only when the user names one, and then add a
## Clarificationssection to that file rather than a new one. - Play back. Before the charter is written, give the user one short paragraph: the reading the run will follow and the
inferreditems they should know about. This is a summary, not a question, and it asks nothing.
Stop rules
- Never ask a question that would not change an acceptance criterion, the plan or a test.
- Never ask more than 5 questions in one session. Inferred items are not capped, but each must still change an acceptance criterion, the plan or a test.
- Stop when every category is
Clear, or its open points are recorded. - Do not edit
ticket.md. The ticket is the user's text; the clarifications are the record of what was inferred from it.
What this skill does not do
- It does not write code or tests, and it does not change the plan. The plan and the charter take its answers as input.
- It does not decide hard-to-undo points silently in a session where a user can answer. Those are asked.
- It does not commit anything.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

