Support multiple issues in dev implementation

[sri-rang]

Summary

• accept one or multiple GitHub issues as dev-impl input
• produce and record one combined approved implementation plan
• implement the complete issue set on a single focused branch
• update the skill UI metadata for multi-issue usage

Validation

• make lint — passed
• make test — passed (7/7 tests)
• make validate — passed

[qodo-code-review]

PR Summary by Qodo

Support multi-issue planning and implementation in dev-impl skill

📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Allow $dev-impl to accept and process multiple GitHub issues in one run.
• Require a single combined plan, recorded back to every referenced issue after approval.
• Standardize on one focused branch for implementing the complete issue set.

Diagram

graph TD
  U[User] --> S["$dev-impl workflow"] --> G["GitHub Issues (1..N)"]
  S --> D[".codex/skills/dev-impl/SKILL.md"]
  S --> C[".codex/skills/dev-impl/agents/openai.yaml"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Keep dev-impl single-issue; add a separate multi-issue skill

• ➕ Avoids changing existing behavior/expectations for current users
• ➕ Allows stricter rules tailored to multi-issue coordination without complicating the base skill
• ➖ Splits documentation and user education across two skills
• ➖ Creates ambiguity about which skill to use for related issues

2. Require an explicit 'batch mode' flag (e.g., $dev-impl --multi)

• ➕ Preserves single-issue as the default mental model
• ➕ Makes multi-issue execution an intentional opt-in
• ➖ Adds interface complexity and extra decision points for users
• ➖ Still requires the same combined-plan and branching guidance

Recommendation: The PR’s approach (treat multiple issues as a single planned/approved batch with one branch and one combined plan mirrored to each issue) is the most operationally consistent for coordinated work. The main tradeoff—changing expectations from single-issue to multi-issue—is mitigated here by making the behavior explicit in both the SKILL.md instructions and the agent’s default prompt.

Files changed (2) +29 / -22

Documentation (1) +27 / -20

SKILL.mdDefine multi-issue dev-impl workflow and approval/branching rules +27/-20

Define multi-issue dev-impl workflow and approval/branching rules

• Updates the skill instructions to accept one or more issues, preserve ordering while deduplicating, and exclude closed issues unless explicitly confirmed. Specifies producing a single combined implementation plan, posting it to every issue after approval, and implementing the full set on one focused branch.

.codex/skills/dev-impl/SKILL.md

Other (1) +2 / -2

openai.yamlAdjust agent UI text and prompt for multi-issue usage +2/-2

Adjust agent UI text and prompt for multi-issue usage

• Updates the display metadata to reflect planning/implementing multiple approved issues and adjusts the default prompt example to include multiple issue numbers with a single plan.

.codex/skills/dev-impl/agents/openai.yaml

[qodo-code-review]

No code issues found._{ⓘ  0 issues published inline · 0 in summary — for nitpicking, see all findings}

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-code-review]

PR approved by Qodo

All merge criteria satisfied — approved by default policy

[qodo-code-review]

Qodo Fixer

No findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR.