ahgraber/skills / plugins/sdd/skills/sdd-archive
sdd-archive
VerifiedUse when completing and archiving a change after all tasks are done and specs are synced. Triggers: "archive the change", "complete this change", "close out the change", "finish the change", "archive".
SDD Archive
Complete a change by moving its directory to the archive.
SPECS_ROOTis resolved by thesddrouter before this skill runs. Replace.specs/with your project's actual specs root in all paths below.
Writing Style
Write the archive report in the voice of a professional technical writer. Prefer ASD-STE100 Simplified Technical English: short sentences, one instruction per sentence, active voice, and one term per concept. Keep identifiers, commands, paths, and RFC 2119 keywords exact.
When to Use
- All tasks in
tasks.mdare complete (- [x]), except the follow-up tasks of recorded overrides - Delta specs have been synced into main specs with
sdd-sync - Ready to close out the change
When Not to Use
- Tasks are incomplete — finish implementation first
- Delta specs exist but haven't been synced — consider running
sdd-syncfirst (no automatic check; user judgement)
Invocation Notice
- Tell the user when this skill is running:
sdd-archive. Skip the notice when the user asked for the skill by name or slash command; spelling and spacing need not match. A phrase from this skill's own trigger list is not a name — naming the work is not naming the skill.
Soft Gate
Check tasks.md for unchecked tasks before archiving.
Do not count a task that a recorded override in design.md names as its follow-up task; tell the user that each such task stays open by design.
If incomplete tasks remain:
"{N} tasks are still incomplete. Archive anyway?"
Wait for user confirmation before proceeding.
Process
Phase 1: Confirm
- Confirm which change to archive (ask if multiple active changes exist)
- Read
tasks.md— count complete vs. total tasks, leaving out override follow-up tasks (see Soft Gate) - If incomplete tasks: issue soft gate warning, wait for user
Phase 2: Check Target
Target path: .specs/changes/archive/YYYY-MM-DD-<change-name>/
Where YYYY-MM-DD is today's date.
If the target already exists:
"Archive target already exists:
.specs/changes/archive/{date}-{name}/. Suggest using{name}-2or waiting until tomorrow."
Stop and ask the user how to proceed.
Phase 3: Move
mkdir -p .specs/changes/archive/
mv .specs/changes/<name>/ .specs/changes/archive/YYYY-MM-DD-<name>/
Confirm the move succeeded by checking the archive path exists.
The change's .verify/ directory (if present, one directory per verify run) must move with the change; mv carries it along, so do not delete it.
Whether it enters the archived commit follows the user's ignore rule for .verify/.
Phase 4: Update Change Order
If .specs/changes/ORDER.md exists, update it per references/sdd-change-formats.md § 6.5:
- Remove the archived change from every section.
- Remove each Starts after entry and each Reasons bullet that names the archived change.
- Remove each shared requirement line that now names fewer than two changes.
- Update Last reviewed.
- If no Starts after entry, no shared requirement, and no
## Not scheduledchange remains, deleteORDER.md.
Check the result against the rules in § 6.4. Every active change directory must appear in exactly one section, and no archived change may appear anywhere.
Phase 5: Report
Archived: .specs/changes/<name>/ → .specs/changes/archive/YYYY-MM-DD-<name>/
Tasks: {N}/{N} complete
Change order: {updated | deleted | no ORDER.md}
Ready to start: {each change in ORDER.md whose Starts after entries are all met, or "none"}
Common Mistakes
- Deleting instead of moving (archive, not delete — change history is preserved)
- Archiving before syncing delta specs into main specs
- Not checking for the target path existence before moving
- Leaving the archived change in
ORDER.mdas a met prerequisite, instead of removing it - Keeping
ORDER.mdafter the remaining changes can apply in any order
References
references/sdd-change-formats.md— change order format and maintenance (§ 6)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |