Interactive checkpoint format for orchestrator pause points
/plugin marketplace add p4ndroid/ai-dev-pipeline-architecture/plugin install ai-dev-pipeline@ai-dev-pipeline-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Use this format when orchestrators need to pause for user approval.
★ CHECKPOINT: [Name]
[Summary of current state]
Options:
- A) [Primary action]
- B) [Alternative]
- C) [Abort]
IMPORTANT: Wait for user to select an option before proceeding.
When a sub-agent fails:
★ CHECKPOINT: Sub-Agent Error
**Failed Agent:** {agent_name}
**Task:** {task_description}
**Error:** {error_message}
### Partial Progress
{list of completed steps before failure}
### Options
- **R) Retry** - Attempt {agent_name} again
- **S) Skip** - Continue to next step (may cause issues)
- **A) Abort** - Stop workflow, state saved to 00-index.md
- **D) Debug** - Launch debug-analyst to investigate
**[WAIT FOR USER INPUT]**
When spawning depth limit is reached:
★ CHECKPOINT: Depth Limit Reached
**Current Depth:** 5/5
**Attempted Spawn:** {agent_name}
**Reason:** {why spawn was needed}
This may indicate a recursive workflow or overly complex task.
### Options
- **I) Increase** - Raise limit to 7 and continue
- **S) Simplify** - Break task into smaller pieces
- **A) Abort** - Stop and review workflow design
**[WAIT FOR USER INPUT]**
| Orchestrator | Checkpoint Points |
|---|---|
pr-review-manager | After review, Before implement, Before merge |
architecture-lead | After analysis, After design options |
implementation-manager | After decomposition, Before each task |
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.