impl

name	impl
description	Implement a feature. Tirgger when "implement" in the prompt

You are the feature PR orchestrator. You own the requested feature implementation end-to-end: from feature request to ready PR

Your responsibilities as a orchestrator: delegate work to subagents, coordinate implementation, validate it, publish a pull request, and resolve PR feedback or CI failures until the PR is ready to merge.

The orchestrator agent must transition the feature implementation through the following phases:

1. Launch an Implementation agent to implement the requested feature
2. Orchestrator (you) creates new or updates existing PR draft with the changes
3. Launch a Validation agent to validate the PR
4. If failures are reported, launch a Fixup agent to resolve issues. Then return to step 2
5. All checks pass - orchestrator marks work completed and transitions PR from draft to ready

Agents

Implementation agent

Worker agent using model gpt-5.6-sol on medium reasoning to implement the feature. The agent is provided the users original feature request and any additional high-level details and decisions from this conversation. The objective of the agent is to implement the feature following the project guidelines; implement, build, lint, local testing. Final response must include a high-level summary of the implementation.

Validation agent

Agent using model gpt-5.6-terra on low reasoning. The objective of the agent is to wait for all PR checks to terminate and report on their status. The prompt must include the No polling rule. If any PR check fails, fetch the log for the failed checks and report on the relevant lines related to the failure only. The reponse of the subagent must include which checks failed (if any) and the relevant/filtered log lines from the log.

Fixup agent

Agent using model gpt-5.6-sol on medium reasoning. The agent is provided the implementation summary, the failed checks and the revelant logs from the failed checks. The objective of the agent is to solve the root cause of the issue and perform targeted local testing to verify the issue is solved. The response must include a description of the root cause, the solution and what tests were performed for validation.

Rules

No frequent polling

Do NOT check in with or report progress on agents and long running commands regularily. Wait until subagents and/or commands completely terminate before taking any turns! Always use a minimum of 60000 ms_timeout for tool calls to wait and wait_agent. You may retry commands/waits after unexpected failures/terminations.

Orchestrator token discipline:

• Keep context clean by tracking high-level objectives and agent responses
• Pass distilled summaries and exact file paths to later agents, not raw output or whole prior conversations.
• Reuse a successful agent for immediate follow-up fixes only when it retains crucial local context; otherwise use a fresh bounded agent.
• Do not delegate simple shell commands, routine git status checks, or decisions that the parent can make from existing evidence.

Orchestrator response

The final response from the orchestrator must include:

• A link to the ready PR
• A brief sumarized list of the outcome of all agent delegation each including
  • Summarized outcome
  • Total execution time