Archive an OpenSpec change
SkillDev toolsArchive a completed RIPDPI OpenSpec change through the fail-closed taskctl lifecycle.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Archive an OpenSpec change skill
What this skill tells your AI
The instructions your AI receives, as published by po4yka/ripdpi in .agents/skills/openspec-archive-change/SKILL.md and read by ahel’s review.
Use this skill only when implementation is complete and the user asks to finalize a change.
- Resolve the active change with
./taskctl openspec cli list --jsonand its linked portfolio task with./taskctl list --json. - Run
./taskctl verify <task-id> --archive-ready. Stop on open mdtask steps, invalid OpenSpec artifacts, missing exact-SHA evidence, or anyrequired/blockedevidence category. - Require portfolio status
review; never treat an agent checkbox as acceptance. - Run
./taskctl openspec archive <change-name>. Never call the upstream archive command directly, pass--no-validate, move a change directory manually, or proceed after a warning. - Run
./taskctl close prepare <task-id> --outcome done --evidence "<concise evidence summary>". - Stop and ask for the terminal-state commit.
close purgeis a later, separately committed step.
For a dropped task, do not archive incomplete behavior deltas as completed. Prepare dropped with an explicit reason and preserve the active change until the owner decides whether to revise or remove it.
Signals
- GitHub stars
- 69
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
openspec-archive-change-po4yka- Source
- github.com/po4yka/ripdpi