Pre-flight verification for PAL MCP server availability
/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 skill to verify PAL MCP server is available before starting workflows that depend on it.
pr-review-manager starts code review workflowarchitecture-lead starts architecture analysismcp__pal__* toolsThe following PAL tools must be available:
| Tool | Purpose | Used By |
|---|---|---|
mcp__pal__codereview | Multi-model code review | code-reviewer |
mcp__pal__consensus | AI consensus building | architecture-lead |
mcp__pal__thinkdeep | Deep analysis | debug-analyst |
mcp__pal__debug | Debugging assistance | debug-analyst |
mcp__pal__analyze | Code analysis | architecture-analyst |
Before starting a workflow, orchestrators MUST:
★ CHECKPOINT: Missing Required Dependency
**Required:** PAL MCP Server
**Status:** Not available
The PAL MCP server is required for this workflow.
### Installation
1. Clone PAL: git clone <pal-repo>
2. Install dependencies: npm install
3. Configure in Claude Code settings
### After Installation
Run this workflow again.
### Options
- **A) Abort** - Stop workflow (recommended)
- **C) Continue** - Proceed without PAL (limited functionality)
**[WAIT FOR USER INPUT]**
Per ADR-003, PAL is a hard dependency. Multi-model consensus is a core value proposition.
If user selects "Continue without PAL":
Add to orchestrator prompt:
## Phase 0: Pre-flight Check
Before starting the workflow:
1. Verify PAL MCP server is available
2. If not available, present the PAL Pre-flight checkpoint
3. Only proceed after confirming PAL availability or user override
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.