rpi-implement

rpi-implement

Field	Value
Kind	skill
Source	.github/skills/rpi/rpi-implement
Invocation	Invoked directly as /rpi-implement, or loaded on demand by referencing agents
Interactive	No

What it does

Follow an approved RPI plan, keep it current as new information comes to light, check off completed work, and keep a condensed changes log. Use when implementation is ready to begin or resume.

When to use it

Use rpi-implement to work through an approved plan. Declare the scope as the full plan, one Pxx phase, or one Pxx-Txx task; the skill starts at the first unchecked dependency-ready item in that scope and works in plan order. It checks each Pxx-Txx marker as soon as its Requirements: hold, runs the checks the plan names, and keeps a condensed changes log in .copilot-tracking/changes/ that describes the behavior or functionality each completed item changed rather than the edits made.

Implementation also keeps the plan current. Checked task markers, implementation-only Guidance: pointers and out-of-scope ## Follow-Up Items are annotations, so normal progress continues. When evidence changes task wording, references, requirements, architecture, capability, safety or dependencies, the implementer updates the affected plan sections directly. An unresolved significant or divergent choice needs your decision before affected work resumes; an evidence-backed clarification does not. A change that needs replanning beyond the affected tasks returns to rpi-plan.

Implementation does not require a plan critique. If you skipped the critique, implementation proceeds normally. When the plan is marked not ready or has unresolved blocking critique findings, the implementer names them and confirms with you before implementing affected tasks.

Reach for a different asset when:

• No approved plan exists. Run rpi-plan first; do not implement from research alone.
• The implementation is finished and you want an acceptance review. Run rpi-review; review is optional.
• The change is small and isolated. Edit directly instead of creating lifecycle artifacts.

Example usage

Run one bounded task:

/rpi-implement plan=.copilot-tracking/plans/2026-09-04/blob-storage-plan.md task=P01-T01

The skill sends one RPI Implement opening with the scope, write boundary, and planned validation, then reports material results as they land. A bounded closeout confirms only its scope:

* Implementation execution: Complete for P01-T01
* Completed markers: P01-T01; remaining active-plan markers: P01-T02, P02-T01, P03-T01
* Validation: `npm run test:py -- tests/storage` passed
* Plan updates: added `Guidance:` to P02-T01 pointing at `BlobStorageClient.upload_stream`
* Review readiness: not ready; P01-T02 and later phases remain

| Artifact                                                                                                                     | Description    |
|------------------------------------------------------------------------------------------------------------------------------|----------------|
| [.copilot-tracking/changes/2026-09-04/blob-storage-changes.md](.copilot-tracking/changes/2026-09-04/blob-storage-changes.md) | Changes record |

## Next Steps

Run `/rpi-implement plan=... task=P01-T02`, or omit `task` to complete the rest of the plan.

A later invocation can implement accepted RV-xxx findings from a review as ordinary work; no second review is required.