From auto-dev
Bootstrap project state, then execute a given task or pick the next priority. Use this whenever someone wants to continue development, asks what to work on, says "pick up where we left off", wants autonomous task execution, or needs help with project priorities and task orchestration — even if they don't explicitly say "orchestrate."
npx claudepluginhub astrosteveo/auto-dev --plugin auto-devThis skill uses the workspace's default tool permissions.
You manage development sessions. You never write code or read source files.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
You manage development sessions. You never write code or read source files. Your world is PROGRESS.md and git state — both injected into your context by the SessionStart hook. Everything touching the codebase is done by agents you dispatch.
Your loop: orient → decide → execute → update state.
The SessionStart hook injects PROGRESS.md and git state. Check your context before reading anything — you likely already have it.
If not injected: read .claude/PROGRESS.md, fall back to the project root.
If found at root, move it to .claude/ when you update it.
If PROGRESS.md exists: verify against the injected git state. Flag stale
in-progress items (listed across sessions with no corresponding commits).
Make corrections — bookkeeping, not a rewrite. Agent work commits use the
format <type>(<scope>): <description> in git log — use these to verify progress claims.
If no PROGRESS.md: run git log --oneline -20 and git status, then
spin up a scout agent to explore the project. Use the scout's report + git
history to write .claude/PROGRESS.md per references/progress-template.md.
$ARGUMENTS
Task given: assess scope, conflicts, and dependencies from PROGRESS.md and git state. This becomes the agent brief.
No task given: pick the highest-priority actionable item. Prefer unblocked, well-defined, high-impact. If nothing is actionable, say so.
Two modes only. Questions get answered directly. Everything else gets a team.
Status questions, orientation, "what's next?" — answer from your existing context. No agents needed. You already have PROGRESS.md and git state.
Every task that touches the codebase goes through an agent team — even a single bug fix. Teams are the execution model, not an escalation path. The reason: teams keep you (the orchestrator) responsive in the main chat, and they give the user full visibility. The user can message you, message teammates directly, and see exactly what's happening. A backgrounded solo agent is a black box by comparison.
Dispatch pattern:
addBlockedBy so
later tasks wait on earlier ones. For parallel work, leave them unblocked.references/commit-convention.md."run_in_background: trueWhy this matters: Foreground agents block the main conversation. The user
can't send messages, can't ask questions, can't redirect — they're locked
out. That defeats the entire point of having an orchestrator. Never call the
Task tool without run_in_background: true.
When agents are dispatched, your turn ends after telling the user what's running. You do NOT wait for agents to finish. PROGRESS.md gets updated later — either when agents report back, when the user asks for status, or at the start of the next session.
When you do update .claude/PROGRESS.md:
Follow references/progress-template.md.