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.
npx claudepluginhub grainulation/grainulator --plugin grainulatorThis skill uses the workspace's default tool permissions.
The user is relaying feedback from stakeholders that should be incorporated into the sprint.
Protects projects from scope creep via requirement triage, stakeholder negotiation, diplomatic refusals, and MVP discipline. Activates on mentions of scope creep, feature requests, or changing requirements.
Aggregates multi-reviewer feedback from content, brand, technical, legal, and strategic categories into prioritized action items, resolves conflicts, and generates synthesis reports.
Resolves requirement ambiguity before implementation by decomposing into decision points and asking targeted questions. Auto-selects depth: default research mode or --light Q&A based on input specificity.
Share bugs, ideas, or general feedback.
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