rpi-implement

RPI Implement

Goal

Deliver the approved outcome using the current plan and phase details as evidence. Keep task completion, implementation evidence, plan maintenance, and validation trustworthy for the caller.

Flow

1. Resolve the exact plan at .copilot-tracking/plans/{{YYYY-MM-DD}}/{{task_slug}}-plan.md, related plan details, and declared invocation scope: the full plan, one Pxx phase, or one Pxx-Txx task. The declared scope limits completion claims and active implementation.
2. Create or continue .copilot-tracking/changes/{{YYYY-MM-DD}}/{{task_slug}}-changes.md using templates/changes-log.md. Record material evidence under descriptive headings tied to plan areas or markers, not per-entry formal IDs.
3. Before substantive source edits or implementation, update the plan checklist, changes log, and any related state tracking artifacts.
   • Send the implementation opening defined in references/implementation.md.
4. Start with the first unchecked dependency-ready plan item in declared scope, then execute eligible items in plan order.
   • Delegate only a whole Pxx phase when it is in declared scope, dependency-ready, independent, parallelizable, and write-disjoint. Its scope, dependencies, disjoint write boundary, and expected evidence return must be clear. The primary implementation agent executes individual Pxx-Txx tasks, consumes phase returns, and retains plan order, plan and changes-record reconciliation, implementation-time plan updates, and completion markers.
   • When stated task completion evidence exists, immediately check the completed Pxx-Txx marker in scope. Check a Pxx phase immediately only when that phase is in scope and completion evidence exists for every task in the phase. Do not check markers outside declared scope.
5. When declared scope finishes, ensure its changes, blockers, completion markers, remaining work, and validation state are current. Report active plan markers outside the scope as remaining work. Report full-plan completion only when the full plan was declared and all of its markers have completion evidence.
6. Classify new implementation information using references/implementation.md: retain ordinary local judgment, apply immediately relevant current-state updates that preserve approved intent, record unrelated work as follow-up-only, and treat a discovery as material only when it requires a new user decision or planning reconsideration.
7. Ask for the smallest decision-critical user input only when available evidence cannot support a responsible user-owned decision. Persist the result in current planning state and the changes record. If the accepted plan must change, pause only affected dependent work and return the current evidence to planning. The confirmed user decision remains authoritative; do not run another critique.
8. Run validation expected by the plan or changed behavior after the approved source or correction batch is complete. Record checks, results, and explicit skip reasons without treating validation alone as permission to resume paused dependent work.
9. Before handing a full-plan or review-ready scope to Review, reconcile plan markers, phase details, completed-work evidence, handoff prose, blockers, remaining work, follow-up items, and validation state.
10. Return the current implementation result to the caller using the return contract below.