at-prompt-creator
Create agent-team orchestrated prompt bundles (orchestrator + sub-prompts) and store them through prompt-manager.
What this skill does
# at-prompt-creator
Create an orchestrated prompt set for complex work:
- 1 main orchestrator prompt
- N focused sub-prompts that can run independently
Use this skill when the user asks for `/create-at-prompt`.
## Inputs
- Task description (same quality bar as `/create-prompt`)
- Optional destination folder under `./prompts/` (never `completed/`)
## Resolve Helpers
```bash
PLUGIN_ROOT=$(jq -r '.plugins."daplug@cruzanstx"[0].installPath' ~/.claude/plugins/installed_plugins.json)
PROMPT_MANAGER="$PLUGIN_ROOT/skills/prompt-manager/scripts/manager.py"
CONFIG_READER="$PLUGIN_ROOT/skills/config-reader/scripts/config.py"
```
Use `prompt-manager` for all prompt writes/reads. Do not create files manually.
## Workflow
### 1. Analyze Complexity and Decompose
Break the task into sub-prompts only when at least one of these is true:
- Work can be parallelized across different file areas/components.
- There are distinct specialist concerns (backend, frontend, tests, infra, docs).
- The task benefits from explicit planner/executor/validator separation.
Keep sub-prompts single-purpose and executable in isolation.
### 2. Draft Sub-Prompts First
Create sub-prompts first so orchestrator delegation can reference exact prompt IDs.
For each sub-task:
```bash
python3 "$PROMPT_MANAGER" create "<subtask-name>" --folder "$FOLDER" --content "$SUB_PROMPT_CONTENT" --json
```
Each sub-prompt must include:
- Clear `<objective>`
- Narrow `<scope>`
- Explicit `<output>` files
- Prompt-local `<verification>` criteria
### 3. Create Orchestrator Prompt
After sub-prompts exist, create one orchestrator prompt that references them.
Use this template structure:
```xml
<objective>
Coordinate multi-agent execution for the parent task using existing sub-prompts.
</objective>
<orchestration>
<phase name="plan">
<!-- Claude native planning and risk check -->
- Confirm assumptions, dependencies, and execution strategy.
- Draft exact Task() orchestration with explicit escalation paths.
</phase>
<phase name="execute" strategy="parallel|sequential">
<!-- Delegation to sub-prompts via /run-prompt -->
<delegate prompt="228a" model="opencode" flags="--worktree" />
<delegate prompt="228b" model="codex" flags="--worktree --loop" />
</phase>
<phase name="validate">
<!-- Claude native integration + merge criteria -->
- Verify outputs are consistent and conflict-free.
- Resolve overlaps before final handoff.
</phase>
</orchestration>
<merge_criteria>
- All sub-prompts completed or explicitly triaged.
- No unresolved file conflicts.
- Validation checks pass.
</merge_criteria>
<output>
- Final integrated summary
- Recommended /run-at-prompt group syntax
</output>
```
The orchestrator body should include explicit Task() delegations so it is executable:
```text
Task(
subagent_type: "at-monitor",
model: "haiku",
run_in_background: true,
prompt: "Launch /run-prompt 228a --model opencode --worktree and return Execution Report format."
)
```
Create orchestrator prompt:
```bash
python3 "$PROMPT_MANAGER" create "<task-name>-orchestrator" --folder "$FOLDER" --content "$ORCHESTRATOR_CONTENT" --json
```
### 4. Emit Execution Options (Decision Tree)
After prompt creation, present:
1. Run orchestrator prompt directly:
```bash
/run-prompt <orchestrator-id> --model claude
```
2. Run sub-prompts with explicit groups:
```bash
/run-at-prompt "220,221 -> 222" --model codex --worktree
```
3. Run sub-prompts with auto dependency inference:
```bash
/run-at-prompt "220 221 222" --auto-deps --dry-run
```
Recommend `--worktree` for any parallel execution. Recommend `--loop` for high-risk prompts.
## Orchestrator Quality Rules
- Plan phase stays Claude-native (research + dependency checks).
- Execute phase delegates via `/run-prompt` only; no ambiguous free-form delegation.
- Validate phase is explicit about pass/fail and merge gates.
- Keep model tiering explicit in delegation metadata where possible.
- Every delegate should be independently runnable.
## Naming Conventions
- Use concise, kebab-case names.
- Suggested naming:
- `<task>-orchestrator`
- `<task>-backend`
- `<task>-frontend`
- `<task>-tests`
- `<task>-docs`
## Failure Handling
- If decomposition is unclear, ask 1-3 targeted clarifying questions.
- If a prompt creation call fails, stop and report exact stderr from prompt-manager.
- Never silently skip sub-prompt generation.
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.