From grainulator
Analyzes sprint claims for type distributions, evidence quality tiers, stale claims over 7 days, velocity metrics, and prediction scoring. Generates HTML retrospective reports.
npx claudepluginhub grainulation/grainulator --plugin grainulatorThis skill uses the workspace's default tool permissions.
The user wants quantitative analysis of the current sprint: claim type distributions, evidence quality, stale claims, and velocity metrics.
Analyzes sprint delivery data like tickets, velocity, and carry-overs from Jira to produce structured retrospective briefs with metrics, observations, prompts, and experiments. Useful for agile retrospectives.
Displays sprint dashboard with claims, conflicts, coverage stats, evidence tiers, claim types, warnings, and decision-tree-based next actions like /resolve or /research.
Conducts project or sprint retrospectives by gathering data from status reports, velocity metrics, and artifacts; structures what went well, improvements, and generates actionable items with owners and due dates. Use at sprint ends, milestones, or reviews.
Share bugs, ideas, or general feedback.
The user wants quantitative analysis of the current sprint: claim type distributions, evidence quality, stale claims, and velocity metrics.
$ARGUMENTS
Optional: --full to generate an HTML retrospective report. --calibrate to run prediction scoring.
Detect the sprint directory:
wheat_status to get the current sprint metadata.claims.json).claims.json file./init to start one."<dir> for subsequent steps.Run type/evidence analysis:
npx @grainulation/harvest analyze <dir>Run stale claim detection:
npx @grainulation/harvest decay <dir> --days 7Display the analytics summary:
Harvest: <sprint-slug>
─────────────────────────────
Claim distribution:
constraint: <n> | factual: <n> | estimate: <n>
risk: <n> | recommendation: <n> | feedback: <n>
Evidence quality:
stated: <n> | web: <n> | documented: <n> | tested: <n> | production: <n>
Weak areas:
- <list any evidence tiers with 0 claims, or types with heavy concentration>
- <flag if >60% of claims share the same type (type monoculture)>
- <flag if >50% of evidence is "stated" or "web" (weak evidence base)>
Stale claims (<n> total):
- <id>: "<summary>" — <age> days stale
- ...
Velocity:
<output from analyze, e.g. claims/day, time between phases>
Suggest full retrospective:
For a full retrospective report:
npx @grainulation/harvest report <dir> -o output/harvest.html
--full, run the report command directly and write the output to output/harvest.html.Recommend calibration if sprint is complete:
Sprint looks complete. Score your predictions:
/calibrate --outcome "what actually happened"
npx @grainulation/harvest calibrate <dir>
--calibrate, run npx @grainulation/harvest calibrate <dir> and display the prediction accuracy results.Suggest next steps based on the findings:
Next steps:
/challenge <stale-id> -- revisit the stalest claim
/witness <weak-id> <url> -- strengthen weak evidence
/blind-spot -- check for structural gaps
/brief -- compile findings into a decision doc
Tailor the suggestions:
/challenge or /research on the stalest/witness or /research/challenge to diversify/brief or /present