ai-dev-framework-template

Run a retrospective analysis on completed work to identify process improvement opportunities. Use when the user wants to review a completed batch or item run, or invoke on-demand with a PR number, branch, or date as scope hint.

Compatibility/advanced alias: resolve a native GitHub epic into a bounded workflow execution scope, with optional delegated review and merge gates. For the recommended starting point, use /run-work <epic-target> instead. Use /run-epic when you need direct control over delegation flags (--delegate-review, --may-merge, --max-risk). For explicit item lists, use /run-items.

Bounded multi-item execute command: advance two or more explicit workflow items through Protocol 90 explicit_list mode. For a single item use $run-item; for an epic use $run-epic; for a read-only portfolio scan use $run-work.

Read-only portfolio scan. No-target scan proposes batches with no dispatch. Two or more targets redirect to $run-items. Single targets redirect to $run-item or $run-epic. No mutation in any mode.

Batch-orchestrate the repository's staged AI development workflow. Use when the user wants Codex to discover what can advance or start across multiple items, propose the largest safe batch by priority and parallelization feasibility, and supervise approved item work until it reaches a real terminal condition.

Primary bounded command: advance exactly one non-epic workflow item. Use when the user asks for /run-item or wants to resume a specific development, branch, PR, or issue with the shared bounded prelude before Protocol 91. /run-item-work is a deprecated alias with identical behavior.

Advance a single workflow item until it reaches a real terminal condition. Use when the user wants Codex to resume or advance one specific development, branch, or PR without scanning the whole portfolio.

Deprecated compatibility alias for /run-item. Identical behavior — prefer $run-item or /run-item for new invocations.

Implement a workflow item in code. Use for full-pipeline implementation, refactors (plan only, no spec), fast-track fixes, or hotfixes using the repository's implementation protocol.

Write an implementation plan for a feature (after spec approval) or a refactor (plan only, no spec). Use when a work item needs to advance into the implementation plan stage.

Sync framework updates from the upstream template into this downstream project. Reads sync-manifest.yaml from the upstream template for the authoritative file list; falls back to the embedded list when the manifest is absent. Use when a downstream project needs to pull in the latest framework files from the template.

Compatibility alias for /post-merge-qa with identical behavior. Prefer /post-merge-qa.

Primary command: QA work already on develop or develop-<slug>. Use when the user asks for /post-merge-qa or /merged-qa-tester (identical alias). Proposes confirmed scope, preflights environment, exercises flows, optional design-asset fidelity, and opens one fix PR for safe defects without a new backlog item.

Command-style Codex alias for graduating an integration branch. Use when the user asks for /graduate-development or wants to merge an integration branch back to develop.

Write a feature spec for the AI development workflow. Use when a new feature needs to move from backlog into the spec stage.

Command-style Codex alias for creating a backlog item. Use when the user asks for /add-backlog-item or wants to create a tracked work item before spec or plan work.

Command-style Codex alias for running a retrospective. Use when the user asks for /retrospective or wants a completed batch or item analyzed.

After a development PR is merged, sync with origin, switch to the merged PR's base branch, pull, verify or delete the remote implementation branch, delete the local branch, and update the related issue in the issue tracker. Use when you want to clean up the local repo post-merge.

Run the automated reviewer loop (and CI loop) for a PR. Use when the user wants to run the reviewer loop on a specific PR or the current branch's PR until it is ready for human review or escalated.

Review implemented changes against the repository's code review workflow. Use when a feature, refactor, fix, or hotfix PR needs review or reviewer feedback needs to be addressed.

Review and refine an implementation plan. Use when a plan draft or plan PR needs review against the repository's plan review protocol.

Review and refine a workflow spec. Use when a spec draft or spec PR needs review against the repository's spec review protocol.

Command-style Codex alias for preparing a release. Use when the user asks for /prepare-release or wants to run the repository release preparation protocol.

Merge all ready PRs in a parallel batch into the target base branch sequentially, auto-resolving trivial CHANGELOG and documentation conflicts, pausing for human input only on non-trivial conflicts, and running post-merge-cleanup for each successfully merged PR. Prints the merge plan for visibility but proceeds immediately without requiring confirmation. Use when a parallel batch of PRs is ready for merge.

Command-style Codex alias for syncing framework updates from the upstream template. Use when the user asks for /sync-template.

Command-style Codex alias for reviewing implementation changes. Use when the user asks for /code-review or wants the repository code review gate.

Command-style Codex alias for running PR automated review and CI loops. Use when the user asks for /run-reviewer-loop or wants a PR driven to readiness.

Run the repository's project setup workflow. Use when initializing a new project from this template or when the user asks Codex to follow the project setup protocol.