agent
Use for full agentic multi-file refactoring or feature work — spec → planner → coder → qa-reviewer → qa-fixer pipeline with rollback. The "do the whole loop" command. Pairs with /siftcoder:agent.
What this skill does
# agent End-to-end agentic loop. Plan → Code → Review → Fix with safety brakes. The single-command equivalent of manually chaining the planner / coder / qa-reviewer / qa-fixer agents. ## When this differs from `/build` - `build` skill → build a feature from a spec, smaller scope, no QA loop - `agent` skill → full multi-agent pipeline with QA and remediation, suited to multi-file refactors and risky features ## When this differs from `/autonomous` - `autonomous` → long-running unattended runs (hours) - `agent` → bounded multi-file pipeline (minutes-to-hours), single goal, gated milestones ## Method 1. **Spec ingest.** User-provided spec or planner-output. If absent, dispatch `planner` agent first. 2. **Pre-flight.** - `git status` — must be clean (or stash) - Scope check — `.siftcoder/scope.json` (and chroot if set) - Checkpoint via `/checkpoint` skill — rollback ref 3. **Plan.** Dispatch `planner` agent → structured plan w/ subtasks. 4. **Approve.** Surface plan to user. Wait for approval (skip in fully-autonomous mode w/ explicit user opt-in). 5. **Execute.** - Sequential subtasks → `coder` agent per subtask - Parallelisable subtasks → `orchestrator` agent → batched dispatch 6. **Review.** Dispatch `qa-reviewer` agent against AC. 7. **Fix.** If qa-reviewer flags issues → dispatch `qa-fixer` agent. 8. **Re-review.** Loop step 6+7 once. If still failing → escalate to user. 9. **Verify.** Tests, lint, typecheck. 10. **Capture.** Memory captures the full run (plan, execution, QA outcomes). ## Output shape ``` # Agent run: <goal> ## Pre-flight ✓ git clean ✓ scope: 14 files in chroot ✓ checkpoint saved: cp-<id> ## Plan (planner agent) T1 refactor src/auth/middleware (deps: none) T2 update tests/auth/* (deps: T1) T3 migrate config schema (deps: none) ... User approval: ✓ (or autonomous mode) ## Execution T1: ✓ done by coder files: 2 changed T3: ✓ done by coder files: 1 changed T2: ✓ done by coder files: 4 changed ## QA Review (qa-reviewer agent) AC1: ✓ pass AC2: ✓ pass AC3: ✗ uncovered — test missing for edge case ## QA Fix (qa-fixer agent) AC3: ✓ fixed — added test in tests/auth/edge.test.ts ## Re-review ✓ all AC pass ## Verification Tests: 412/412 ✓ Lint: ✓ Types: ✓ ## Final Files changed: 7 Tests added: 5 Memory: summary id <X> Rollback: git reset --hard cp-<id> ## Recommended next Manual smoke test → commit → merge ``` ## Rules - **Pre-flight required.** Clean tree + scope + checkpoint before any write. - **User approval gate** by default. Autonomous mode is opt-in per run, not per project. - **Loop cap.** Max 1 review-fix cycle. Second failure → escalate. - **Rollback path explicit.** Always one git command away from before. - **Memory captures the whole run** — re-runs of similar tasks reuse the plan. ## Anti-patterns - Skipping pre-flight (no rollback = catastrophe) - Treating qa-reviewer output as ignorable - Looping review-fix indefinitely (cap at 1; escalate) - Running on dirty tree ## When NOT to use - Single-file change — `/fix` or `/build` - Long autonomous run (hours) — `/autonomous` (different brake system) - Pure investigation — `/investigate` ## Subagent dispatch - `planner` → plan - `orchestrator` → batched parallel dispatch - `coder` → implementation per subtask - `qa-reviewer` → AC validation - `qa-fixer` → bounded remediation ## Value over native CC CC has parallel `Task` calls + `Plan`. CC doesn't enforce: pre-flight checkpointing, plan approval gate, AC-validated review, scope-bounded fixer, single-cycle review-fix cap. The end-to-end discipline IS the value — turns "agentic refactor" from risky into auditable.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.