Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Show a snapshot of the current sprint -- claims, conflicts, coverage, and next actions.
Skill Claude CodeCodex
Publish the current sprint to Confluence as a page with structured content.
Skill Claude CodeCodex
Corroborate a claim against an external source URL.
MCP server Claude CodeCodexCursor +2
Research-driven development framework — structured claims, compiled evidence, deterministic output. Runs locally from the @grainulation/wheat npm package.
Instructions file CodexOpenCode
Instructions for grainulation/wheat, covering wheat research sprint, claims system and key commands.
Command
You are scanning the claim set for structural gaps — not what's wrong, but what's missing. Read CLAUDE.md for sprint context, claims.json for existing claims, and compilation.json for coverage data.
Command
You are compiling the final decision brief for this Wheat sprint. This is the Bran compilation step — deterministic output from resolved claims.
Command
You are checking what actually happened after a sprint's recommendations were implemented. This closes the feedback loop by comparing predictions to outcomes.
Command
You are stress-testing a specific claim by researching the strongest possible counter-argument with real evidence. Read CLAUDE.md for sprint context and claims.json for existing claims.
Command
You are connecting an external tool or data source to this Wheat sprint. Connected sources provide higher-quality evidence than web research alone.
Command
You are running the evaluation phase of the current Wheat sprint. This is the honesty phase — where claims meet data.
Command
You are processing feedback from stakeholders for this Wheat sprint. Feedback introduces new claims (usually constraints or direction changes) that may trigger re-evaluation.
Command
You are generating a self-contained briefing optimized for a successor — someone who needs to continue this sprint, not a stakeholder making a decision. Read CLAUDE.md, claims.json, and compilation.json.
Command
You are initializing a new Wheat research sprint. Have a focused conversation with the user to establish.
Command
You are merging claims from another sprint into the current one. This is for when two teams researched the same problem independently and need to combine their findings.
Command
You just finished a slash command or a batch of work. The user monitors via Farmer on their phone and cannot see CLI text output.
Command
You are generating a presentation for this Wheat sprint. Same Bran compilation gate as /brief.
Command
You are building a proof-of-concept for the current Wheat sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
Command
You are pulling knowledge from external sources into the current Wheat sprint. Read CLAUDE.md for sprint context and claims.json for existing claims.
Command
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
Command
You are researching a topic for the current Wheat sprint. Read CLAUDE.md for sprint context and claims.json for existing claims.
Command
You are manually resolving a conflict between claims that the compiler couldn't auto-resolve (same evidence tier).
Command
You are generating the current status dashboard for this Wheat sprint.