skills/implement-local-plan/SKILL.md
Implement a development plan from local plan files with work report tracking. Use when the user wants to execute a local development plan from `.github/plans/` or `.github/reports/`, implement backlog items step by step, or create work reports for completed tasks.
npx skillsauth add jim60105/copilot-prompt implement-local-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement a development plan from local plan files with systematic work report tracking.
--signoff. Write the commit in English..github/reports/.Development progress is tracked within the .github/reports directory. Before starting any new work, review prior reports to stay aligned with ongoing development. Treat all past reports as immutable references — do not edit or revise them. Upon task completion, generate a new comprehensive work report. Refer to naming conventions of existing files to determine an appropriate filename.
Reports must include a detailed account of the work performed, encompassing all relevant code modifications and corresponding test outcomes.
Implement the plan step by step, following the instructions provided in the plans/ directory. Each step should be executed in sequence, ensuring that all requirements are met and documented appropriately.
development
Generate images via the Stable Diffusion WebUI / Forge HTTP API (AUTOMATIC1111-compatible `/sdapi/v1/*`). Use when the user wants to (1) discover or pick a model / extra module (TE/VAE) / sampler / scheduler / style preset from a running sd-webui server, (2) generate an image with a given prompt (txt2img), (3) check generation progress, (4) cancel/interrupt an in-flight generation, (5) inspect or change a global sd-webui option (e.g. active checkpoint), or (6) test connectivity. This skill talks to a *generic* sd-webui-compatible server (AUTOMATIC1111, Forge, reForge, sd-webui-forge-classic). Do NOT trigger for requests that are purely writing the prompt itself.
testing
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
development
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
data-ai
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.