Jira estimator
Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: 'estimate KEY', 'story points for KEY', 'how complex is KEY'. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).From its SKILL.md
npx -y skills add ngocsangyem/MeowKit --skill jira-estimatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 316 tokens by cl100k_base, as published. Nobody here has run it
mk:jira-estimator
Forks to the jira-estimator agent. Read-only heuristic estimation. If a prior mk:jira-evaluator report exists at tasks/reports/jira-evaluate-*-{KEY}.md, the agent reads it and incorporates the complexity signals.
Triggers
- "estimate PROJ-123"
- "story points for PROJ-123"
- "how complex is PROJ-123 in points?"
Examples
- Cold estimate: "estimate PROJ-456 — give me a Fibonacci range and reasoning."
- Post-evaluate: "I just evaluated PROJ-456; now estimate it."
See also
- Agent:
../../agents/jira-estimator.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework,estimation-guide}.md - Domain refs (cross-link, lives under jira-time):
../jira-time/references/estimation-guide.md— story-point vs hours-based estimation tradeoffs
- Peer intelligence:
mk:jira-evaluator(run first for complexity signals),mk:jira-analyst(full ticket synthesis) - Peer execution:
mk:jira-issue(update --custom-fields '{"customfield_10016": N}'writes the estimate),mk:jira-fields(discover instance-specific story-points field ID),mk:planning-engine(capacity analysis)
Gotchas
- (none yet)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.