claude-command-bridge

name: claude-command-bridge description: Execute workflows defined in .claude/commands from Codex. Use when the user references /speckits/*, Speckits workflow steps, /pr-develop, or asks to reuse existing Claude command prompts.

Claude Command Bridge

Use this skill as an adapter between Claude command files and Codex execution.

Command map

• /pr-develop -> .claude/commands/pr-develop.md
• /speckits/specify -> .claude/commands/speckits/specify.md
• /speckits/clarify -> .claude/commands/speckits/clarify.md
• /speckits/plan -> .claude/commands/speckits/plan.md
• /speckits/tasks -> .claude/commands/speckits/tasks.md
• /speckits/analyze -> .claude/commands/speckits/analyze.md
• /speckits/implement -> .claude/commands/speckits/implement.md
• /speckits/checklist -> .claude/commands/speckits/checklist.md
• /speckits/constitution -> .claude/commands/speckits/constitution.md
• /speckits/taskstoissues -> .claude/commands/speckits/taskstoissues.md

Execution rules

1. Parse the request into one target command from the map.
2. Load only the mapped command file and follow it as the primary workflow.
3. Treat user text after the command name as $ARGUMENTS.
4. If the command references prerequisite scripts or templates, execute/read those files before generating output.
5. If the command requires interaction (for example choice selection), ask concise blocking questions and continue.
6. Preserve expected output locations and file names from the command spec.
7. Report completion with:

• command executed
• files created or updated
• key next command suggested by the workflow handoff

Speckits flow reference

Default sequence: /speckits/specify -> /speckits/clarify -> /speckits/plan -> /speckits/tasks -> /speckits/analyze -> /speckits/implement

Auxiliary commands:

• /speckits/checklist
• /speckits/constitution
• /speckits/taskstoissues

Project-specific guardrails

For code changes requested by Speckits commands, also read .claude/project-rules.md and enforce its FSD constraints.