How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

workflow-resolve-issue - Prompt

Name: workflow-resolve-issue
Author: williaby

Prompt file imported from williaby/PromptCraft (.claude/commands/workflow-resolve-issue.md). Fill in {{arguments}} before use. Copyright stays with the author.

Workflow Resolve Issue (Orchestrator)

Systematically resolve any project issue through modular workflow orchestration: {{arguments}}

Usage Options

quick phase X issue Y - Essential workflow steps only (30-45 min)
standard phase X issue Y - Full workflow with validation (60-90 min)
expert phase X issue Y - Minimal prompts for experienced users (15-30 min)

Workflow Components

This orchestrator executes the following workflow components in sequence:

1. Scope Analysis (`/project:workflow-scope-analysis`)

Purpose: Define issue boundaries and prevent scope creep

Analyzes issue definition and acceptance criteria
Creates scope boundary documentation
Identifies dependencies and unclear requirements
Estimated Time: 10-15 minutes

2. Plan Validation (`/project:workflow-plan-validation`)

Purpose: Create and validate implementation plan

Develops action plan aligned with acceptance criteria
Validates scope boundaries and removes scope creep
Optional IT manager consultation via Zen
Estimated Time: 10-15 minutes

3. Implementation (`/project:workflow-implementation`)

Purpose: Execute approved plan with quality standards

Implements solution using subagents and MCP orchestration
Follows security best practices and coding standards
Maintains progress tracking and scope adherence
Estimated Time: Variable based on issue complexity

4. Review Cycle (`/project:workflow-review-cycle`)

Purpose: Comprehensive testing and multi-agent validation

Pre-commit validation and quality gate checks
Multi-agent review (O3 testing, Gemini review)
Consensus validation and final approval
Estimated Time: 15-30 minutes

Workflow Execution

Quick Mode (`quick`)

/project:workflow-scope-analysis quick phase X issue Y
/project:workflow-implementation quick phase X issue Y
/project:workflow-review-cycle quick phase X issue Y

Standard Mode (`standard`)

/project:workflow-scope-analysis phase X issue Y
/project:workflow-plan-validation phase X issue Y
/project:workflow-implementation phase X issue Y
/project:workflow-review-cycle phase X issue Y

Expert Mode (`expert`)

/project:workflow-scope-analysis detailed phase X issue Y
/project:workflow-plan-validation expert phase X issue Y
/project:workflow-implementation subagent phase X issue Y
/project:workflow-review-cycle consensus phase X issue Y

Required Output

Each workflow component produces specific deliverables:

Scope Analysis: Scope boundary document with clear inclusions/exclusions
Plan Validation: Approved implementation plan document
Implementation: Working code meeting acceptance criteria with progress tracking
Review Cycle: Comprehensive validation report with multi-agent consensus

User Approval Gates

CRITICAL: The workflow includes mandatory user approval points:

After scope analysis (for boundary confirmation)
After plan validation (before implementation begins)
After review cycle (for final acceptance)

Error Handling and Recovery

Missing documentation: Auto-generate templates or provide clear setup instructions
Invalid arguments: Interactive prompts for clarification with examples
Workflow interruption: Checkpoint capability to resume from any component
Scope creep detection: Automatic boundary validation and user consultation
Quality gate failures: Clear remediation steps with specific commands

Development Philosophy Integration

All workflow components follow the project's core principles:

Reuse First: Leverage existing solutions from ledgerbase, FISProject, .github
Configure Don't Build: Use Zen MCP Server, Heimdall MCP Server, AssuredOSS packages
Focus on Unique Value: Build only PromptCraft-specific functionality

Examples

# Quick issue resolution (essential steps only)
/project:workflow-resolve-issue quick phase 1 issue 3

# Standard workflow (recommended)
/project:workflow-resolve-issue standard phase 2 issue 7

# Expert mode (minimal prompts)
/project:workflow-resolve-issue expert phase 1 issue 1

Install workflow-resolve-issue and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Workflow Resolve Issue (Orchestrator) Systematically resolve any project issue through modular workflow orchestration: {{arguments}} ## Usage Options - `quick phase X issue Y` - Essential workflow steps only (30-45 min) - `standard phase X issue Y` - Full workflow with validation (60-90 min) - `expert phase X issue Y` - Minimal prompts for experienced users (15-30 min) ## Workflow Components This orchestrator executes the following workflow components in sequence: ### 1. Scope Analysis (`/project:workflow-scope-analysis`) **Purpose**: Define issue boundaries and prevent scope creep - Analyzes issue definition and acceptance criteria - Creates scope boundary documentation - Identifies dependencies and unclear requirements - **Estimated Time**: 10-15 minutes ### 2. Plan Validation (`/project:workflow-plan-validation`) **Purpose**: Create and validate implementation plan - Develops action plan aligned with acceptance criteria - Validates scope boundaries and removes scope creep - Optional IT manager consultation via Zen - **Estimated Time**: 10-15 minutes ### 3. Implementation (`/project:workflow-implementation`) **Purpose**: Execute approved plan with quality standards - Implements solution using subagents and MCP orchestration - Follows security best practices and coding standards - Maintains progress tracking and scope adherence - **Estimated Time**: Variable based on issue complexity ### 4. Review Cycle (`/project:workflow-review-cycle`) **Purpose**: Comprehensive testing and multi-agent validation - Pre-commit validation and quality gate checks - Multi-agent review (O3 testing, Gemini review) - Consensus validation and final approval - **Estimated Time**: 15-30 minutes ## Workflow Execution ### Quick Mode (`quick`) ```bash /project:workflow-scope-analysis quick phase X issue Y /project:workflow-implementation quick phase X issue Y /project:workflow-review-cycle quick phase X issue Y ``` ### Standard Mode (`standard`) ```bash /project:workflow-scope-analysis phase X issue Y /project:workflow-plan-validation phase X issue Y /project:workflow-implementation phase X issue Y /project:workflow-review-cycle phase X issue Y ``` ### Expert Mode (`expert`) ```bash /project:workflow-scope-analysis detailed phase X issue Y /project:workflow-plan-validation expert phase X issue Y /project:workflow-implementation subagent phase X issue Y /project:workflow-review-cycle consensus phase X issue Y ``` ## Required Output Each workflow component produces specific deliverables: 1. **Scope Analysis**: Scope boundary document with clear inclusions/exclusions 2. **Plan Validation**: Approved implementation plan document 3. **Implementation**: Working code meeting acceptance criteria with progress tracking 4. **Review Cycle**: Comprehensive validation report with multi-agent consensus ## User Approval Gates **CRITICAL**: The workflow includes mandatory user approval points: - After scope analysis (for boundary confirmation) - After plan validation (before implementation begins) - After review cycle (for final acceptance) ## Error Handling and Recovery - **Missing documentation**: Auto-generate templates or provide clear setup instructions - **Invalid arguments**: Interactive prompts for clarification with examples - **Workflow interruption**: Checkpoint capability to resume from any component - **Scope creep detection**: Automatic boundary validation and user consultation - **Quality gate failures**: Clear remediation steps with specific commands ## Development Philosophy Integration All workflow components follow the project's core principles: - **Reuse First**: Leverage existing solutions from ledgerbase, FISProject, .github - **Configure Don't Build**: Use Zen MCP Server, Heimdall MCP Server, AssuredOSS packages - **Focus on Unique Value**: Build only PromptCraft-specific functionality ## Examples ```bash # Quick issue resolution (essential steps only) /project:workflow-resolve-issue quick phase 1 issue 3 # Standard workflow (recommended) /project:workflow-resolve-issue standard phase 2 issue 7 # Expert mode (minimal prompts) /project:workflow-resolve-issue expert phase 1 issue 1 ```

{ "prompt": "# Workflow Resolve Issue (Orchestrator)\r\n\r\nSystematically resolve any project issue through modular workflow orchestration: {{arguments}}\r\n\r\n## Usage Options\r\n\r\n- `quick phase X issue Y` - Essential workflow steps only (30-45 min)\r\n- `standard phase X issue Y` - Full workflow with validation (60-90 min)\r\n- `expert phase X issue Y` - Minimal prompts for experienced users (15-30 min)\r\n\r\n## Workflow Components\r\n\r\nThis orchestrator executes the following workflow components in sequence:\r\n\r\n### 1. Scope Analysis (`/project:workflow-scope-analysis`)\r\n\r\n**Purpose**: Define issue boundaries and prevent scope creep\r\n\r\n- Analyzes issue definition and acceptance criteria\r\n- Creates scope boundary documentation\r\n- Identifies dependencies and unclear requirements\r\n- **Estimated Time**: 10-15 minutes\r\n\r\n### 2. Plan Validation (`/project:workflow-plan-validation`)\r\n\r\n**Purpose**: Create and validate implementation plan\r\n\r\n- Develops action plan aligned with acceptance criteria\r\n- Validates scope boundaries and removes scope creep\r\n- Optional IT manager consultation via Zen\r\n- **Estimated Time**: 10-15 minutes\r\n\r\n### 3. Implementation (`/project:workflow-implementation`)\r\n\r\n**Purpose**: Execute approved plan with quality standards\r\n\r\n- Implements solution using subagents and MCP orchestration\r\n- Follows security best practices and coding standards\r\n- Maintains progress tracking and scope adherence\r\n- **Estimated Time**: Variable based on issue complexity\r\n\r\n### 4. Review Cycle (`/project:workflow-review-cycle`)\r\n\r\n**Purpose**: Comprehensive testing and multi-agent validation\r\n\r\n- Pre-commit validation and quality gate checks\r\n- Multi-agent review (O3 testing, Gemini review)\r\n- Consensus validation and final approval\r\n- **Estimated Time**: 15-30 minutes\r\n\r\n## Workflow Execution\r\n\r\n### Quick Mode (`quick`)\r\n\r\n```bash\r\n/project:workflow-scope-analysis quick phase X issue Y\r\n/project:workflow-implementation quick phase X issue Y\r\n/project:workflow-review-cycle quick phase X issue Y\r\n```\r\n\r\n### Standard Mode (`standard`)\r\n\r\n```bash\r\n/project:workflow-scope-analysis phase X issue Y\r\n/project:workflow-plan-validation phase X issue Y\r\n/project:workflow-implementation phase X issue Y\r\n/project:workflow-review-cycle phase X issue Y\r\n```\r\n\r\n### Expert Mode (`expert`)\r\n\r\n```bash\r\n/project:workflow-scope-analysis detailed phase X issue Y\r\n/project:workflow-plan-validation expert phase X issue Y\r\n/project:workflow-implementation subagent phase X issue Y\r\n/project:workflow-review-cycle consensus phase X issue Y\r\n```\r\n\r\n## Required Output\r\n\r\nEach workflow component produces specific deliverables:\r\n\r\n1. **Scope Analysis**: Scope boundary document with clear inclusions/exclusions\r\n2. **Plan Validation**: Approved implementation plan document\r\n3. **Implementation**: Working code meeting acceptance criteria with progress tracking\r\n4. **Review Cycle**: Comprehensive validation report with multi-agent consensus\r\n\r\n## User Approval Gates\r\n\r\n**CRITICAL**: The workflow includes mandatory user approval points:\r\n\r\n- After scope analysis (for boundary confirmation)\r\n- After plan validation (before implementation begins)\r\n- After review cycle (for final acceptance)\r\n\r\n## Error Handling and Recovery\r\n\r\n- **Missing documentation**: Auto-generate templates or provide clear setup instructions\r\n- **Invalid arguments**: Interactive prompts for clarification with examples\r\n- **Workflow interruption**: Checkpoint capability to resume from any component\r\n- **Scope creep detection**: Automatic boundary validation and user consultation\r\n- **Quality gate failures**: Clear remediation steps with specific commands\r\n\r\n## Development Philosophy Integration\r\n\r\nAll workflow components follow the project's core principles:\r\n\r\n- **Reuse First**: Leverage existing solutions from ledgerbase, FISProject, .github\r\n- **Configure Don't Build**: Use Zen MCP Server, Heimdall MCP Server, AssuredOSS packages\r\n- **Focus on Unique Value**: Build only PromptCraft-specific functionality\r\n\r\n## Examples\r\n\r\n```bash\r\n# Quick issue resolution (essential steps only)\r\n/project:workflow-resolve-issue quick phase 1 issue 3\r\n\r\n# Standard workflow (recommended)\r\n/project:workflow-resolve-issue standard phase 2 issue 7\r\n\r\n# Expert mode (minimal prompts)\r\n/project:workflow-resolve-issue expert phase 1 issue 1\r\n```", "variables": [ "arguments" ], "notes": "Systematically resolve any project issue through modular workflow orchestration: ${arguments}", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/williaby/PromptCraft", "path": ".claude/commands/workflow-resolve-issue.md", "ref": "fccc4eb8ac8e0f570396685ec8113f74008ff9e4", "url": "https://github.com/williaby/PromptCraft/blob/fccc4eb8ac8e0f570396685ec8113f74008ff9e4/.claude/commands/workflow-resolve-issue.md", "key": "williaby/PromptCraft/.claude/commands/workflow-resolve-issue.md" } } }

workflow-resolve-issue

About

Workflow Resolve Issue (Orchestrator)

Usage Options

Workflow Components

1. Scope Analysis (`/project:workflow-scope-analysis`)

2. Plan Validation (`/project:workflow-plan-validation`)

3. Implementation (`/project:workflow-implementation`)

4. Review Cycle (`/project:workflow-review-cycle`)

Workflow Execution

Quick Mode (`quick`)

Standard Mode (`standard`)

Expert Mode (`expert`)

Required Output

User Approval Gates

Error Handling and Recovery

Development Philosophy Integration

Examples

Install workflow-resolve-issue and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

Workflow Resolve Issue (Orchestrator)

Usage Options

Workflow Components

1. Scope Analysis (/project:workflow-scope-analysis)

2. Plan Validation (/project:workflow-plan-validation)

3. Implementation (/project:workflow-implementation)

4. Review Cycle (/project:workflow-review-cycle)

Workflow Execution

Quick Mode (quick)

Standard Mode (standard)

Expert Mode (expert)

Required Output

User Approval Gates

Error Handling and Recovery

Development Philosophy Integration

Examples

Install workflow-resolve-issue and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

1. Scope Analysis (`/project:workflow-scope-analysis`)

2. Plan Validation (`/project:workflow-plan-validation`)

3. Implementation (`/project:workflow-implementation`)

4. Review Cycle (`/project:workflow-review-cycle`)

Quick Mode (`quick`)

Standard Mode (`standard`)

Expert Mode (`expert`)