Apply an approved change proposal

VerifiedSafe

Implement and apply an approved change proposal following structured steps and guardrails.

Sby Skills Guide Bot
DevelopmentIntermediate
007/23/2026
Claude CodeCursor
#change-proposal#implementation#structured-workflow#tasks

Recommended for

Our review

Implements and applies an approved change proposal by following a structured process.

Strengths

  • Encourages minimal and focused implementations
  • Follows a clear sequence of steps with task tracking
  • References multiple documents for full context

Limitations

  • Requires a specific directory structure (changes/<id>)
  • Depends on the prompter tool for commands and context
When to use it

Use this skill when you need to implement a pre-approved change with clearly defined tasks.

When not to use it

Do not use it for exploratory or unplanned changes that require creativity and back-and-forth.

Security analysis

Safe
Quality score90/100

The skill instructs reading and editing files, updating checklists, and using internal tooling; no destructive or exfiltrating actions are present.

No concerns found

Examples

Apply a change proposal
Apply the change proposal with id 42. Read the proposal, design, and tasks files, then implement the changes step by step.
Implement tasks from a proposal
I want to implement the tasks listed in changes/15/tasks.md. Please follow the apply skill process.

name: apply description: Implement and apply an approved change proposal

<!-- PROMPTER:START -->

Guardrails

  • Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
  • Keep changes tightly scoped to the requested outcome.
  • Refer to prompter/AGENTS.md (located inside the prompter/ directory—run ls prompter if you don't see it) if you need additional Prompter conventions or clarifications.

Steps Track these steps as TODOs and complete them one by one.

  1. Read changes/<id>/proposal.md, design.md (if present), and tasks.md to confirm scope and acceptance criteria.
  2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
  3. Confirm completion before updating statuses—make sure every item in tasks.md is finished.
  4. Update the checklist after all work is done so each task is marked - [x] and reflects reality.
  5. Reference prompter list or prompter show <item> when additional context is required.

Reference

  • Use prompter show <id> --json --deltas-only if you need additional context from the proposal while implementing.
<!-- PROMPTER:END -->
Related skills