From agentic-loop
Scaffold the agentic-loop template into the current project directory: copies the worker shim scripts, routing-policy CLAUDE.md, .env.example, run-state directory and per-project README. Use when the user wants to set up the orchestrated multi-model agentic loop in a new or existing project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-loop:initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Copy the agentic-loop template into the current project directory. The plugin
Copy the agentic-loop template into the current project directory. The plugin
root is two levels up from this skill's base directory (this file lives at
<plugin-root>/skills/init/SKILL.md). Resolve it first:
PLUGIN_ROOT="$(cd "<this skill's base directory>/../.." && pwd)"
Safety check. If the target directory already contains a scripts/
directory, a CLAUDE.md, or a .agentic/ directory, list what would be
overwritten and ask the user before proceeding. Never clobber silently.
Copy, from $PLUGIN_ROOT, into the project:
mkdir -p scripts/lib .agentic/artifacts factory/specs .claude/workflows
cp -R "$PLUGIN_ROOT/scripts/." scripts/
cp "$PLUGIN_ROOT/templates/.env.example" .env.example
cp "$PLUGIN_ROOT/templates/LEARNINGS.md" LEARNINGS.md
cp "$PLUGIN_ROOT/templates/PROJECT_README.md" AGENTIC_LOOP.md
cp -R "$PLUGIN_ROOT/templates/agentic-state/." .agentic/
cp "$PLUGIN_ROOT/templates/factory-spec.md" factory/spec-template.md
cp "$PLUGIN_ROOT/templates/statusline-usage.sh" scripts/statusline-usage.sh
cp "$PLUGIN_ROOT/templates/workflows/factory.js" .claude/workflows/factory.js
chmod +x scripts/*.sh scripts/lib/*.sh
CLAUDE.md: if the project has no CLAUDE.md, copy
$PLUGIN_ROOT/templates/CLAUDE.md as-is. If one exists, append the
template's content under a # Agentic Loop heading instead (show the user
the diff).
.gitignore: append the lines from
$PLUGIN_ROOT/templates/gitignore-snippet if not already present
(.env and .agentic/ must be ignored). If the project has no
.gitignore, create one from the snippet.
Do NOT copy any secrets. Only .env.example is copied; the user fills
.env themselves.
Optional hardening — mention (don't apply unasked): the spawn-budget
PreToolUse hook in $PLUGIN_ROOT/templates/hooks-spawn-guard.json can be
merged into the project's .claude/settings.json.
6b. Factory setup (mention; apply only if the user wants the
spec→build→review loop): the usage gate needs the statusline mirror —
add to .claude/settings.json:
{"statusLine": {"type": "command", "command": "scripts/statusline-usage.sh"}}
factory/specs/ is COMMITTED (it is the coordination bus between
sessions), unlike .agentic/. Point the user at docs/factory.md in the
plugin root for the day-mode run recipe.
./scripts/doctor.sh and showing the user its
output, then point them at AGENTIC_LOOP.md for the remaining checklist
(fill .env, verify subscription login, dry-run one loop). Mention the
opt-ins once, without enabling anything: /agentic-loop:config observability on records every operation to a local event log and renders
run trees (docs/observability.md), and /agentic-loop:config lists the
other default-off flags (minimize, grill, guards, summarize).The four native subagents (loop-planner, loop-worker-cheap,
loop-consolidator, loop-reviewer) ship with the plugin itself and are
available in every project where the plugin is enabled — nothing to copy.
npx claudepluginhub thedull/agentic-loop --plugin agentic-loopGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.