refinement-context
Skill6 starsChanged 24 days agoNo licenceView on GitHub
Where to look for a ticket's context while refining it, and how to write it down — which source answers each question (the team wiki for decisions and proposals, the code and GitHub PRs for how things work today, the task tracker (Jira, GitHub Projects, Asana…) for previous work, read-only database and log tools for production data, the document store for drawings and release files), the rules (every fact with source and date, verified or inference, contradictions written down, only SELECT and counts in production, a search limit) and the "Context" section left in the description. With two example tickets. Use when starting to refine a ticket, before writing its criteria, or when someone asks "what already exists for this?" or "how does X work today?". Invoke as /refinement-context [TICKET-KEY].
In this repository18 other files it gives its agents.
- acceptance-criteriaSkill
- app-designSkill
- ci-cdSkill
- credentialsSkill
- definition-of-readySkill
- feature-flagsSkill
- gate-policiesSkill
- gitflowSkill
- grafana-dashboardsSkill
- kubectlSkill
- observabilitySkill
- pull-requestSkill
- rollout-planSkill
- secret-or-settingSkill
- skill-designSkill
- task-trackerSkill
- test-appsSkill
- ticket-lifecycleSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
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.