Structured Autonomy Implement
Execute an existing implementation plan step-by-step, checking off items and stopping at plan-defined boundaries without extra code.
Overview
structured-autonomy-implement is an agent skill most often used in Build (also Ship) that carries out a supplied implementation plan exactly, updating checkboxes and stopping at plan STOP markers.
Install
npx skills add https://github.com/github/awesome-copilot --skill structured-autonomy-implementWhat is this skill?
- Hard gate: responds with "Implementation plan is required." if no plan input
- Implements only plan-specified changes; no drive-by refactors
- Inline plan updates with markdown checkboxes per completed item
- Runs build or test commands from the plan and stops at explicit STOP instructions
- Mandatory plan input or the agent refuses to implement
Adoption & trust: 8.5k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your coding agent keeps adding unplanned changes or skipping steps because there is no enforced plan-following workflow.
Who is it for?
Builders with a markdown implementation plan who want predictable, minimal-diff agent execution.
Skip if: Exploratory spikes, refactors without a plan, or situations where you want the model to redesign architecture on the fly.
When should I use this skill?
You have an approved implementation plan and need the agent to execute only those steps, update checkboxes, run plan tests, and stop at STOP.
What do I get? / Deliverables
The plan document shows checked completed steps, only specified code ships, and the agent stops when the plan demands user review.
- Plan file with updated checkboxes
- Code changes limited to plan scope
- Test or build verification per plan
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the execution shelf because the skill only runs when a written implementation plan exists and code changes are authorized stepwise. PM subphase reflects plan-driven execution—markdown checklists, step completion, and handoff stops—not open-ended feature design.
Where it fits
Work through the next unchecked section of a feature plan without adding unlisted files.
Complete API changes listed in step 3 only, then run the plan’s integration test command.
Finish verification steps embedded in the plan before stopping for human review.
How it compares
Use instead of free-form "just implement feature X" when you need plan fidelity—not a brainstorming or gap-analysis workflow.
Common Questions / FAQ
Who is structured-autonomy-implement for?
Solo and indie builders using agentic IDEs who already write stepwise implementation plans and need strict adherence during coding runs.
When should I use structured-autonomy-implement?
During Build when executing checkbox plans; during Ship when the plan includes test or build verification steps before merge; not during Idea when no plan exists yet.
Is structured-autonomy-implement safe to install?
It constrains scope to an explicit plan but still edits code and may run shell tests; review the Security Audits panel on this page and keep secrets out of plan files.
SKILL.md
READMESKILL.md - Structured Autonomy Implement
You are an implementation agent responsible for carrying out the implementation plan without deviating from it. Only make the changes explicitly specified in the plan. If the user has not passed the plan as an input, respond with: "Implementation plan is required." Follow the workflow below to ensure accurate and focused implementation. <workflow> - Follow the plan exactly as it is written, picking up with the next unchecked step in the implementation plan document. You MUST NOT skip any steps. - Implement ONLY what is specified in the implementation plan. DO NOT WRITE ANY CODE OUTSIDE OF WHAT IS SPECIFIED IN THE PLAN. - Update the plan document inline as you complete each item in the current Step, checking off items using standard markdown syntax. - Complete every item in the current Step. - Check your work by running the build or test commands specified in the plan. - STOP when you reach the STOP instructions in the plan and return control to the user. </workflow>