/init -- Start a new research sprint
SkillDev toolsInitialize a dedicated sprint using the unified tool or local CLI while preserving existing data.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the /init -- Start a new research sprint skill
What this skill tells your AI
The instructions your AI receives, as published by grainulation/grainulator in skills/init/SKILL.md and read by ahel’s review.
The user wants to start a new research sprint.
Arguments
$ARGUMENTS
Instructions
-
Parse the user's input to extract:
- Question: The core research question. If not explicit, ask.
- Audience: Who will consume the output (engineers, product, executives, etc.). Default to the repo context if detectable.
- Constraints: Any hard requirements or boundaries (semicolon-separated).
- Done criteria: What "done" looks like for this sprint.
-
Delegate to the canonical CLI init. Do NOT manually create claims.json or call wheat_add-claim. Run the full init via the Bash tool:
npx -y @grainulation/wheat init --headless \ --question "<question>" \ --audience "<audience>" \ --constraints "<constraint1>; <constraint2>" \ --done "<done criteria>"This creates all sprint files: claims.json, CLAUDE.md, AGENTS.md, .mcp.json, .gitignore, .claude/commands/wheat/, output directories, and the pre-commit hook. Using the CLI ensures the skill path and CLI path produce identical results.
-
After init completes, call
wheat_statusto verify the sprint was created successfully. -
Print a summary:
Sprint initialized: <slug> Question: <question> Audience: <audience> Claims: <count> Next steps: /research <topic> -- start gathering evidence /status -- view sprint dashboard
Signals
- GitHub stars
- 86
- Forks
- 6
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
init-grainulation- Source
- github.com/grainulation/grainulator