refinement-agent-skills
AGENTS.md2 starsChanged 14 days agoMITView on GitHub
Read this file before taking any action in this repository. Single source of truth for agents. .claude/CLAUDE.md (Claude Code) and GEMINI.md (Gemini CLI) only import this file; Codex, Cursor, and Copilot read it directly. AI workflow changes belong here. refinement-skills is an agent skills package for software requirements refinement in en-US and pt-BR: from meeting transcripts to QA test plans, driven by socratic examination. It is not the workspace where User Stories are analyzed; it is installed into target workspaces.…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository65 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
- ask-refinementSkill
- bootstrap-contextSkill
- configure-refinementSkill
- meeting-minutesSkill
- qa-planSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Self-contained: every skill invoked across workflows lives directly under skills/.
- Distinctive: line 20
No em-dash or en-dash in any repository prose.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md: package constitution
Read this file before taking any action in this repository.
Single source of truth for agents.
.claude/CLAUDE.md(Claude Code) andGEMINI.md(Gemini CLI) only import this file; Codex, Cursor, and Copilot read it directly. AI workflow changes belong here.
What this repository is
refinement-skills is an agent skills package for software requirements refinement in en-US and pt-BR: from meeting transcripts to QA test plans, driven by socratic examination. It is not the workspace where User Stories are analyzed; it is installed into target workspaces. Package vocabulary lives in CONTEXT.md; architectural decisions in docs/adr/, in the format of skills/socratic-examination/ADR.md. A skill installed from outside this repository may assume other homes for the two, a GLOSSARY.md at the root for instance; here these are the ones that hold, and project instructions outrank a skill's assumption.
- Skill source:
skills/<name>/SKILL.md, one folder per skill, no buckets. Each folder containsagents/openai.yamlwith Codex metadata. - Self-contained: every skill invoked across workflows lives directly under
skills/. No external third-party package dependencies, nor references to one. - Manifest:
.claude-plugin/plugin.jsonlists every skill inskills/;.claude-plugin/marketplace.jsonmakes the repository its own marketplace.
Invariants
namein frontmatter matches the folder name. Canonical instructions in en-US; frontmatter keys in English.- Workflows and support skills (
bootstrap-context,refine-story,qa-plan,requirements-discovery,meeting-minutes,which-flow,ask-refinement,configure-refinement) are user-invoked:disable-model-invocation: trueandpolicy.allow_implicit_invocation: falseinopenai.yaml. The primitivessocratic-examinationandrequirements-rigorare model-invoked: thedescriptionis the trigger that decides when they fire. A user-invoked skill cannot be called by another skill; what a workflow needs from another skill, it calls from a primitive or performs itself. - Any rule used by more than one workflow lives in
requirements-rigororsocratic-examination, once. Workflows point there; they do not repeat rules. - No em-dash or en-dash in any repository prose. Rewrite with commas, colons, or periods.
- Any new or renamed skill must be added to
plugin.json,README.md, and thewhich-flowrouter. A router that does not know a skill is a router that lies. prompts/is generated fromskills/viascripts/build-prompts.mjsand never edited manually. When a skill changes, run the build; the validator rejects outdated prompts. Any new reference to a file or the Skill tool inside a skill requires an adaptation rule in the build script, otherwise it fails.
Definition of Done
node scripts/validate-skills.mjs and claude plugin validate . --strict green; node scripts/build-prompts.mjs executed after any change in skills/. Commit messages follow Conventional Commits; commit and push only when requested by the user.
Writing style
Every step concludes with a checkable, rigorous completion criterion. References used only by specific branches live in sibling files linked from SKILL.md; what every branch requires stays inline. Any sentence that does not change agent behavior is pruned. State the desired behavior instead of forbidding the undesired one. Keep each meaning in a single place.
How this package is built
The package is built with the engineering skills derived from mattpocock/skills and maintained locally in both .claude/skills/ (Claude Code) and .agents/skills/ (Antigravity), with zero global dependency: a decision becomes a spec and tickets, and /implement and /implement-spec run the ticket preflight in docs/agents/ticket-preflight.md first and end on the Definition of Done above instead of a test suite this repository does not have. Those skills are the toolchain that builds the package, not a dependency of it: nothing under skills/ references them, and the self-containment invariant is about the package. Every SKILL.md outside skills/ declares metadata.internal: true and stays identical across .claude/skills/ and .agents/skills/ so npx skills add installs only skills/ into target workspaces.
Agent skills
Construction configuration carries a build- prefix, because two of these filenames without it are names the package itself writes into a target workspace, and one repository cannot hold both meanings.
Issue tracker
Specs and tickets live as versioned markdown under docs/tickets/<feature-slug>/. See docs/agents/build-issue-tracker.md.
Triage labels
The five canonical roles, as Status: strings inside each ticket. See docs/agents/build-triage-labels.md.
Domain docs
Single context: the glossary is CONTEXT.md and the ADRs are in docs/adr/. See docs/agents/build-domain.md.
Dogfooding and evals
scripts/link-skills.sh links skills/* into ~/.claude/skills, ~/.agents/skills, and ~/.gemini/config/skills to dogfood skills within this repository. Evals live in evals/, following the Anthropic skill-creator format; scripts/grade-output.mjs runs automated assertions on artifacts. The complete harness layer is documented in docs/agents/harness.md.
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.

