applylisted
Install: claude install-skill xsyetopz/claudetto
The tool is `mcp__claudetto-openspec__openspec`.
1. Pick the change: the name the user gave, else the one change `{action:"status"}` lists. Several changes and no name: ask which.
2. Validate first: `{action:"validate", change}`. On any ERROR or WARNING, name each issue (path and message), fix it through the update skill, and validate again; ask the user when a fix needs a requirement choice, because implementation needs a settled contract.
3. `{action:"status", change}`. Read the files it lists (proposal, design, specs, tasks.md) before the first edit.
4. Work the unticked tasks in order. Keep each edit to its task, plus each defect that blocks it; add a task line for such a fix, because tasks.md records the delivered scope. After a task is done, change its `- [ ]` to `- [x]` in tasks.md, in the same turn.
5. Work every unticked task your tools can do before you stop, because a task left for the user waits a whole turn. When one task is blocked, go on with the next one it does not block. Stop only when each task left needs a decision from the user, hits a denial, or needs a step only the user can take: a command such as `sudo` or a login, or a physical step such as connecting a device. Then wait for the user's answer.
6. When each task is ticked, run the verify skill on the change, because a ticked task is a claim and verify is its check. For each gap it finds, untick the task behind it, close the gap as verify says, tick it again, and run verify once more.
## Ending A Pau