Convert post-delivery feedback into a gated next-version plan.
npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill iterate-rcsnyder
Please help me install this Agent Skill. Skill: iterate Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/iterate Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill iterate-rcsnyder
iterate helps convert real-world post-delivery feedback, deferred work, and known limitations into a clear, test-aware plan for the next version, without losing the audit trail of what was already shipped.
Ask the agent to iterate on your shipped project by reading the existing scaffolding, delivery notes, and new feedback in docs/input/, then propose v2 changes and wait for your confirmation before building.
High-intent search queries and answers about installing and using this skill.
To plan a next-version release, you can convert post-delivery feedback and deferred work into a gated iteration proposal. This process reconstructs the project state from git history and scaffolding artifacts before proposing changes and waiting for your confirmation.
You need to preserve the audit trail during software iteration when adding features or fixing bugs where prior scope and constraints must be maintained. This approach reconstructs project state from version history to ensure continuity.
When planning a new version, you should check existing tests before proceeding and explicitly preserve contradictions in the proposal. This test-aware handling ensures known limitations and conflicts are maintained rather than smoothed over.
The best way to convert client feedback and technical debt into a change plan is to collect inputs from deferred items and bugs, produce an iteration proposal, and require explicit confirmation before updating scope and re-entering the build phase.
Yes, you can use automated context recovery to reconstruct a project's current state from version history, scaffolding artifacts, and delivery notes. This ensures the iteration proposal respects the existing architecture and constraints.
A limitation of re-entering the pipeline is that it requires a confirmation checkpoint before updating scope or design. The re-entry phase is determined by architecture impact, meaning significant changes may restart the entire analysis phase.
elithrarAnalyze session history and git state to generate structured commit-message summaries.
B0yZ4kr14Review completed feature artifacts for debugging remnants and code-quality risks.
ZaxbyHubRun the full test suite on the unmodified codebase before code changes.
rstacruzAutomate post-change verification with preflight checks, targeted tests, and manual validation.
