at-prompt-runner
Orchestrate multi-prompt execution with phase groups, optional auto-deps, and model-tiered agent roles.
What this skill does
# at-prompt-runner
Run existing prompts using agent-team orchestration.
Use this skill when the user invokes `/run-at-prompt`.
## Group Syntax
- `->` separates sequential phases.
- `,` separates prompts inside the same phase (parallel).
Examples:
- `220,221 -> 222,223 -> 224`
- `220 -> 221,222,223 -> 224`
- `220`
Reference parse output:
```json
[
{"phase": 1, "prompts": [220, 221], "strategy": "parallel"},
{"phase": 2, "prompts": [222, 223], "strategy": "parallel"},
{"phase": 3, "prompts": [224], "strategy": "parallel"}
]
```
## Resolve Helpers
```bash
PLUGIN_ROOT=$(jq -r '.plugins."daplug@cruzanstx"[0].installPath' ~/.claude/plugins/installed_plugins.json)
AT_RUNNER="$PLUGIN_ROOT/skills/at-prompt-runner/scripts/at_runner.py"
PROMPT_MANAGER="$PLUGIN_ROOT/skills/prompt-manager/scripts/manager.py"
```
## CLI Contract
```bash
python3 "$AT_RUNNER" parse "220,221 -> 222,223 -> 224"
python3 "$AT_RUNNER" parse "220 221 222" --auto-deps
python3 "$AT_RUNNER" validate "220,221 -> 222"
python3 "$AT_RUNNER" plan "220,221 -> 222" --model codex --worktree --json
```
## Required Execution Flow
### 1. Parse Input
- If user passes explicit groups, parse directly.
- If user passes space-separated prompts with `--auto-deps`, infer group order.
### 2. Validate Prompt References
Run:
```bash
python3 "$AT_RUNNER" validate "$GROUPS" [--auto-deps]
```
If validation fails, stop and report missing prompt IDs.
### 3. Auto-Deps Mode (`--auto-deps`)
When `--auto-deps` is set:
- Read prompt contents via prompt-manager.
- Spawn `at-planner` (`model: sonnet`) to review inferred dependencies.
- Ask user to confirm proposed group syntax before execution.
- Do not execute any `/run-prompt` command until confirmation is explicit.
Planner output should include:
- Proposed group syntax
- Dependency rationale per phase
- Any uncertainty/assumptions
### 4. Build Plan
Run:
```bash
python3 "$AT_RUNNER" plan "$GROUPS" --model "$MODEL" [--worktree] [--loop] [--validate] [--json]
```
If `--dry-run` is set:
- Show plan and generated `/run-prompt` commands only.
- Do not execute anything.
### 5. Execute Phase-by-Phase
For each phase:
- Launch one `at-monitor` task per prompt (`model: haiku`, `run_in_background: true`).
- Each monitor launches `/run-prompt ...` through tmux and produces an Execution Report.
- Collect reports via `TaskOutput()` and triage in orchestrator.
- Monitors only report and flag; they do not choose retries, merges, or architecture changes.
Decision rules:
- All reports `OK` -> continue to next phase.
- Any `ESCALATE` -> inspect evidence and resolve before proceeding.
- Complex unresolved failure -> spawn `at-fixer` (`model: opus`).
- File overlap/conflicts -> spawn `at-merger` (`model: sonnet`).
### 6. Optional Final Validation (`--validate`)
Spawn `at-validator` (`model: sonnet`) after all phases complete.
Validator decides:
- PASS -> done
- RETRY -> rerun specific prompts
- ESCALATE -> call `at-fixer` with explicit log line references
## Model Tiering (Mandatory)
- `at-monitor`: `haiku`
- `at-planner`: `sonnet`
- `at-validator`: `sonnet`
- `at-merger`: `sonnet`
- `at-fixer`: `opus` (only on escalation)
Do not assign sonnet/opus to monitor role.
## Monitor Contract (haiku)
Monitor agents are mechanical watchers. They do not debug or choose strategy.
Each report must include:
- log path
- exit code
- last 20 lines
- triage flags with line references
Report format requirement:
`ESCALATE|OK: {description} (see log lines N-N if applicable)`
## Flags
- `--model <model>`: default model for delegated `/run-prompt` commands
- `--auto-deps`: infer phase ordering from prompt contents
- `--validate`: append final validator phase
- `--worktree`: run each prompt in isolated worktree
- `--loop`: enable verification loop per prompt
- `--dry-run`: show plan only
## Orchestrator Prompt Pattern
Use explicit role-based Task calls:
```text
Task(subagent_type: "at-monitor", model: "haiku", run_in_background: true, prompt: "...phase command...")
Task(subagent_type: "at-validator", model: "sonnet", prompt: "...review reports...")
Task(subagent_type: "at-merger", model: "sonnet", prompt: "...resolve overlap...")
Task(subagent_type: "at-fixer", model: "opus", prompt: "...complex failure details...")
```
Always pass log path + line ranges when escalating.
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.