Stats
Actions
Tags
From grainulator
Records stakeholder feedback as f### claims (constraints or feedback), tags by role, detects conflicts via wheat_compile, and suggests next steps like /resolve. Useful for sprint corrections or direction changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grainulator:feedbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user is relaying feedback from stakeholders that should be incorporated into the sprint.
The user is relaying feedback from stakeholders that should be incorporated into the sprint.
$ARGUMENTS
Parse the feedback: Identify what the stakeholder said. This could be:
Create feedback claims as f### claims:
constraint for hard requirements, feedback for opinions/preferencesstated (stakeholder said it, not independently verified)Check for conflicts: Does this feedback contradict existing claims? If a stakeholder says "budget is $10K max" but research shows a solution at $15K, that's a conflict. Set conflicts_with on both claims.
Run wheat_compile to surface any new conflicts.
Print result:
Feedback recorded:
- <f001>: <summary>
- <f002>: <summary>
Conflicts introduced: <N>
Next steps:
/resolve -- resolve any new conflicts
/research <topic> -- investigate new questions from feedback
/challenge <id> -- test if feedback contradicts existing evidence
npx claudepluginhub grainulation/grainulator --plugin grainulatorAggregates user feedback from Dovetail, Productboard, Notion, Linear, and GitHub into themes, surfaces top unaddressed signal, and maps to current roadmap. Produces FEEDBACK.md for downstream PM skills.
Cross-references structured review findings against an implementation plan, classifies each finding into an action category, applies concrete edits, and produces a traceability summary.