autoimplement

Implements an existing plan end to end with testing, review loops, and CI verification.

294|16|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/osolmaz/pi-workflows --skill autoimplement-osolmaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoimplement
Source: https://github.com/osolmaz/pi-workflows/tree/main/skills/autoimplement
Command: npx skills add https://github.com/osolmaz/pi-workflows --skill autoimplement-osolmaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved implementation plan into a finished, reviewed, and CI-verified pull request requires many coordinated steps—coding, testing, code review rounds, PR comment handling, and CI monitoring—which are easy to do inconsistently or leave unfinished. ## Core Features & Use Cases - Plan-driven implementation: Executes an existing plan end to end without devising a new one, and re-plans via autoplan only when new evidence invalidates the current plan. - Review and CI loop: Runs pi-reviewer against the base branch until no P0/P1 findings remain, addresses valid PR comments, and verifies CI/CD is green before finishing. - Workflow integration: Starts the built-in Pi Workflows autoimplement workflow with a complete structured input covering scope, constraints, workspace mode, verification checks, and merge authorization. - Use Case: After approving a plan for a new feature, ask the agent to autoimplement it; it creates a task branch, implements and tests the changes, opens a PR, iterates on review findings, and reports the PR link with validation results. ## Quick Start Use autoimplement to implement the approved plan in docs/plans, test it, run pi-reviewer until no P0/P1 issues remain, and open a pull request without merging.

Frequently Asked Questions about autoimplement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an approved plan automatically with an AI agent?▼

Invoke the autoimplement skill with the plan or its canonical document, the repository path, and a scope statement. It starts the built-in autoimplement workflow, which implements, tests, reviews, and verifies CI before opening a pull request.

How does autoimplement handle code review findings?▼

It runs pi-reviewer against the base branch in a loop, fixing all P0 and P1 findings until none remain. Rounds with only P2 or lower findings are addressed proportionately without forcing another full review run.

Does autoimplement merge the pull request automatically?▼

No. It merges only when the user explicitly requested a merge or a standing instruction authorizes it. Otherwise it leaves the pull request ready and reports the PR link with validation results.

What happens if the plan becomes invalid during implementation?▼

When implementation, review, or CI evidence invalidates the plan, the skill invokes autoplan with the previous plan and new evidence, then continues from the revised plan. Local implementation bugs stay in the normal fix loop.

Can autoimplement run without the Pi Workflows extension?▼

Yes. Outside Pi or when the workflow is unavailable, it falls back to manual steps: implement the plan, test it, run pi-reviewer rounds, address PR comments, and verify CI/CD before finishing.

When should I not use autoimplement?▼

Do not use it when no clear existing plan exists, since it does not devise an initial plan and will stop as blocked. Use autoplan first to produce a plan, then run autoimplement on it.