Summary
During an Any Managed Agents runtime/runner implementation discussion, Codex repeatedly responded with single-step local next actions instead of invoking the ak-plan leader workflow to decompose the broad product goal into assigned tasks and full lifecycle execution. The user had to explicitly correct the workflow expectation.
Command
Skill invocation context: user requested loading AK Plan and using it for future large project work.
Expected
For large product/runtime goals, the agent should switch to the ak-plan lifecycle: detect repo/board, understand current state, draft a task plan, preview it for confirmation, create tasks, assign available workers, monitor PRs, review/merge, and continue until completion.
Actual
The agent initially tried to handle the runtime/runner work as a single local implementation thread and discussed only immediate next steps.
Context
- ak version: not captured
- OS: macOS local Codex session
- Runtime: codex
- Auth type: user
- Board: h3061qmn
- Repo: 6x5c3hd2
Reproduction
- Ask Codex to resolve a broad product implementation gap in an AK-enabled repo.
- Observe Codex defaulting to local next-step planning instead of loading ak-plan.
- User has to explicitly instruct Codex to load AK Plan.
Proposed Skill Change
Strengthen ak-plan trigger guidance with: “When a user asks to complete a broad product goal, close multiple implementation gaps, or coordinate end-to-end validation in an AK-enabled repository, Codex should invoke ak-plan by default instead of proposing a single-turn local implementation plan.”
Summary
During an Any Managed Agents runtime/runner implementation discussion, Codex repeatedly responded with single-step local next actions instead of invoking the ak-plan leader workflow to decompose the broad product goal into assigned tasks and full lifecycle execution. The user had to explicitly correct the workflow expectation.
Command
Skill invocation context: user requested loading AK Plan and using it for future large project work.
Expected
For large product/runtime goals, the agent should switch to the ak-plan lifecycle: detect repo/board, understand current state, draft a task plan, preview it for confirmation, create tasks, assign available workers, monitor PRs, review/merge, and continue until completion.
Actual
The agent initially tried to handle the runtime/runner work as a single local implementation thread and discussed only immediate next steps.
Context
Reproduction
Proposed Skill Change
Strengthen ak-plan trigger guidance with: “When a user asks to complete a broad product goal, close multiple implementation gaps, or coordinate end-to-end validation in an AK-enabled repository, Codex should invoke ak-plan by default instead of proposing a single-turn local implementation plan.”