sizing
Skill10 starsChanged 21 days agoMITView on GitHub
Pre-cycle Feature sizing workflow that assesses Features from Jira using T-shirt sizes (XS–XXL), produces per-team effort breakdowns (DEV, QE, UX, UI, DOCS), and writes results back to Jira. Accepts a single Feature or all Features in a Fix Version for batch sizing. Use when sizing Features for cycle planning, prioritizing a release backlog, or evaluating whether a Feature fits in a cycle. Activated by commands: /ingest, /assess, /apply.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ruujOnChain/HedgeFund-Skillstheir own version, first seen Nov 8, 2026
- y0n1n1/financial-skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ruujOnChain/HedgeFund-Skills★ 17same name
- y0n1n1/financial-skills★ 1same name
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-readySkill
- bugfixSkill
- code-reviewSkill
- cve-fixSkill
- designSkill
- docs-writerSkill
- e2eSkill
- implementSkill
- kcsSkill
- prdSkill
- rebase-stackSkill
- skill-reviewerSkill
- gh-stackSkill
- report-bugSkill
- triageSkill
- ui-designSkill
- ui-implementSkill
- ux-designSkill
The file
We split this skill 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 17
If the user invoked a specific command (e.g., /assess, /apply), read commands/{command}.md and follow it.
- Distinctive: line 22
If a step fails or produces unexpected output (e.g., Jira MCP errors, network failures, invalid issue keys), stop and report the error to …
≈ “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.
Files
Sizing Workflow Orchestrator
Quick Start
- If the user invoked a specific command (e.g.,
/assess,/apply), readcommands/{command}.mdand follow it. - Otherwise, read
skills/controller.mdto discover the input and route it through the phase dispatcher.
If a step fails or produces unexpected output (e.g., Jira MCP errors, network failures, invalid issue keys), stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md. The scripts/ helpers compact source data, validate AI judgments, calculate derived values, and render artifacts; use JSON artifacts between phases.
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.