name: claude-command-integration description: > Integration phase for reusable command workflow development. Use when planning, designing, building, testing, validating, or refining a reusable command workflow as it moves through a full delivery lifecycle. Triggers include drafting the command spec, locking interfaces, wiring runtime placement, scoring quality, running live scenarios, or choosing the right re-entry point after a failure.

Command Integration

Place the workflow where the target runtime discovers it and confirm it is visible and callable in context.

Intent Router

Load reference files on demand only when the corresponding topic is active:

• references/placement-and-discovery.md — Load when wiring the workflow into plugin or repo-local discovery paths

Quick Start

[ ] Capture the current command spec
[ ] Complete the required outputs for this phase
[ ] Record evidence for the gate
[ ] Hand off the evidence to the next phase

Phase Workflow

Start from the current command spec and tighten only the decisions owned by this phase. Work forward until the gate is satisfied, then hand the evidence to the next phase in the family. Keep the workflow description portable even when the runtime wiring is specific to one environment.

Example Evidence

| Target surface | Path or config | Verification |
|---|---|---|
| Shared plugin | <path> | Workflow appears in discovery list |
| Project-local config | <path> | Workflow resolves without manual patching |

Gate

Integration is complete when discovery succeeds, one live invocation works, and any required local settings are documented.

Safety Notes

Use explicit paths and documented config surfaces. Avoid hidden machine-local assumptions that other users cannot reproduce.

Resource Index