grainulator

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.

Generate a compiled decision brief from the current sprint's claims.

Generate a presentation deck from the compiled sprint data.

Size-efficient URL fetch with semantic extraction. Use for ad-hoc web research when you want content without the raw HTML overhead.

Corroborate a claim against an external source URL.

Intent router that detects user intent from plain messages and dispatches to the appropriate skill.

Sprint analytics — type distributions, stale claims, velocity, prediction scoring

Multi-sprint orchestration — view dependency graph, dispatch next ready sprint

Initialize a new research sprint with a question, audience, and constraints.

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.

Score past predictions against actual outcomes. Closes the feedback loop.

Record stakeholder input — new constraints, corrections, or direction changes.

Adjudicate conflicts between claims that the compiler flagged.

Structural gap analysis -- find what the sprint has not considered.

Adversarial testing of a specific claim. Try to disprove it.

Pull a sprint from Confluence and import it as local claims.

Execute a multi-pass research investigation, adding claims with evidence.

Publish the current sprint to Confluence as a page with structured content.

Show a snapshot of the current sprint -- claims, conflicts, coverage, and next actions.