Skill

init

Initializes a new research sprint by parsing question, audience, constraints, and done criteria, then runs Wheat CLI via npx to create sprint files, hooks, and directories. Verifies setup and prints summary.

Bash

Node

developer-tools

automation

npx claudepluginhub grainulation/grainulator --plugin grainulator

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The user wants to start a new research sprint.

SKILL.md

Similar Skills

research

Executes multi-pass research on topics for sprints, adding 3-5 evidence-based claims per pass to claims.json using web search, DeepWiki for GitHub repos, and file tools.

grainulator

begin

Initializes projects: detects existing code, questions for requirements, researches via subagents, scopes needs, generates roadmap.

7 files9 tools

pbr

gsd:new-project

Initializes new software projects via questioning, optional research, requirements, and roadmap generation. Creates .planning/PROJECT.md, REQUIREMENTS.md, ROADMAP.md, config.json, STATE.md.

5 tools

gsd

Stats

Stars82

Forks6

Last CommitApr 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/init -- Start a new research sprint

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_status to 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

/init -- Start a new research sprint

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_status to 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