Noodle
Operate the Noodle CLI, explain commands, find flags, create/edit .noodle.toml config.
Install
npx skills add poteto/noodle --skill noodle -g -a claude-code -y- Repository
- poteto/noodle577
- Category
- Writing
- Updated
- 8mo ago
- License
- MIT
- Context cost
- Lightabout 1,185 tokens
- Runs scripts
- No, instructions only
What it does
Operate the Noodle CLI, explain commands, find flags, create/edit .noodle.toml config. Also covers writing skills for Noodle: the orders pipeline, task-type schedule fields, stage composition, and the orders-next.json schema. Use when running noodle commands, editing .noodle.toml, writing or updating a skill's schedule field, authoring new task-type skills, or asking "how to run noodle", "noodle help", "configure noodle".
Noodle
Skills that run themselves. Write skills with a schedule: field describing when they should run. Noodle's scheduler agent reads those descriptions, writes orders, and the loop spawns agents in isolated worktrees to do the work.
How the Loop Works
- Brief, Noodle gathers project state into
.noodle/mise.json(backlog, active agents, history, capacity, registered skills) - Schedule, the scheduler agent reads mise, writes
.noodle/orders-next.json - Dispatch, Noodle promotes orders and spawns agent sessions
- Execute, each agent runs in its own worktree with the assigned skill
- Merge, completed work merges back to main
Skills
A skill is a directory with a SKILL.md. The body is the agent's instructions. The frontmatter is metadata.
General skills (no schedule:) are invoked directly by agents. Examples: commit, debugging.
Scheduled skills (with schedule:) run autonomously. The scheduler reads the schedule: value as prose and uses judgment to decide when conditions are met.
---
name: quality
description: Post-cook quality gate.
schedule: "Follow-up stage after execute. Cross-provider review preferred."
---
Skills live in .agents/skills/ by default. Paths in skills.paths are searched in order; first match wins.
For the full guide on writing skills, orders, and schedule fields, see references/skill-authoring.md.
Configuration
Noodle reads .noodle.toml at project root. Scaffolded on first noodle start. Most projects only need:
mode = "supervised" # auto | supervised | manual
[routing.defaults]
provider = "claude"
model = "claude-opus-4-6"
[skills]
paths = [".agents/skills"]
Full config reference: references/configuration.md
CLI
All commands accept --project-dir (default: current directory, env: NOODLE_PROJECT_DIR).
