grainulation

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

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

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

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

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

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

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

Adjudicate conflicts between claims that the compiler flagged.

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

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.

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

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

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

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.

Corroborate a claim against an external source URL.

Generate a presentation deck from the compiled sprint data.

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

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

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