grainulator
By grainulation
Orchestrate structured research sprints for Claude Code: initialize projects with Wheat claims system, conduct multi-pass research adding evidence-tiered claims, resolve conflicts and risks, generate WCAG-compliant HTML briefs presentations and retrospectives, manage multi-sprint dependencies, integrate with Confluence.
npx claudepluginhub grainulation/grainulator --plugin grainulatorComponent Overview
Setup Configuration
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
tips_levelBackground tips level: on (all tips), quiet (conflicts only), off (disabled)
${user_config.tips_level}Component Details
Skills (19)
Pull a sprint from Confluence and import it as local claims.
Publish the current sprint to Confluence as a page with structured content.
Corroborate a claim against an external source URL.
Structural gap analysis -- find what the sprint has not considered.
Generate a compiled decision brief from the current sprint's claims.
Score past predictions against actual outcomes. Closes the feedback loop.
Adversarial testing of a specific claim. Try to disprove it.
Record stakeholder input — new constraints, corrections, or direction changes.
Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.
Sprint analytics — type distributions, stale claims, velocity, prediction scoring
Fast pre-flight health check for all Grainulator MCP servers. Pings each server once, reports status in a table, and provides exact fix commands for any that are down. Use before starting any Grainulator session to avoid wasting time on MCP disconnections.
Initialize a new research sprint with a question, audience, and constraints.
Multi-sprint orchestration — view dependency graph, dispatch next ready sprint
Generate a presentation deck from the compiled sprint data.
Execute a multi-pass research investigation, adding claims with evidence.
Adjudicate conflicts between claims that the compiler flagged.
Intent router that detects user intent from plain messages and dispatches to the appropriate skill.
Guide the user through verifying Grainulator's MCP servers are running, explain what each server does, handle optional dependencies, and initialize a first sprint if none exists. Use when the plugin is first installed, when MCP servers fail to connect, or when the user asks for help setting up Grainulator.
Show a snapshot of the current sprint -- claims, conflicts, coverage, and next actions.
Hooks (1)
MCP Servers (4)
README
Similar Plugins
stepwise-research
Multi-agent deep research plugin with parallel web searches and synthesis
Modifies files
Hook triggers on file write and edit operations
External network access
Connects to servers outside your machine
Help us improve
Share bugs, ideas, or general feedback.