gen-idea
Skill3 starsChanged 18 days agoApache-2.0View on GitHub
Phase 1 of plan-then-build. Turns a loose idea into a draft file with a main direction and alternatives, checked against the repository. Writes no code. Run with /baton:gen-idea "<idea>", then /baton:gen-plan, then /baton:rlcr.
In this repository17 other files it gives its agents.
- author-flowSkill
- cleanup-flame-chaseSkill
- cleanup-ralphSkill
- continue-loopSkill
- fixed-interruptSkill
- flame-chaseSkill
- flowsSkill
- gen-planSkill
- goalSkill
- parallel-chase-prSkill
- parallel-chaseSkill
- protocolSkill
- ralph-loopSkill
- recursive-lean-proverSkill
- rlarSkill
- rlcrSkill
- stateful-ralphSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
If <out> doesn't exist, send the drafter one repair message saying so.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
gen-idea
Arguments: $ARGUMENTS
Load the run protocol first (Skill tool → baton:protocol; if that fails, Read ${CLAUDE_PLUGIN_ROOT}/skills/protocol/SKILL.md) and follow it. This is a doc-only flow: no run branch, no commits, and it may run on a dirty tree. This file only adds what is specific to gen-idea.
Flags
--out <path>: defaultideas/<slug>.md, where<slug>is a short kebab-case name you derive from the idea.--directions N: how many directions to explore, default 5.--force: allow overwriting an existing output file.
Roles
| Role | subagent_type | Model | Session |
| drafter | baton:worker | worker model | one turn, named <run-id>-drafter (kept only for one repair) |
Turn prompt
BATON gen-idea · turn 1/1 · role drafter · run <run-id>
IDEA:
<task, verbatim>
Turn this loose idea into a draft. Write no code and change no file other than <out>.
Explore <N> directions. Check each against this repository (read only what each direction depends on). Then write <out> with these sections:
1. Idea: the idea restated in two or three sentences.
2. Main direction: what, why, and how it fits this repository, with file references.
3. Alternatives: each direction you didn't pick, with its trade-off against the main one.
4. Open questions: decisions a human should make.
5. Risks.
Report status: done when the file is written.After the turn
- If
<out>doesn't exist, send the drafter one repair message saying so. If it still doesn't exist, stop as failed. - Compare
git status --porcelainwith what it showed before the run. If the drafter changed any other file, list those files to the user rather than reverting them, since the tree may have been dirty before. - Report the path and tell the user to read and edit it, then run
/baton:gen-plan <out>.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.