ahgraber/sdd-archive
skills/sdd-archive/SKILL.md
Use 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".
$ install --global
skillsauthnpx skillsauth add ahgraber/skills sdd-archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 3:10 AM8.5s1 file scanned
SKILL.md
- name:
- sdd-archive
- description:
- |-
- Use 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.
Invocation Notice
- Inform the user when this skill is being invoked by name:
sdd-archive.
When to Use
- All tasks in
tasks.mdare complete (- [x]) - 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)
Soft Gate
Check tasks.md for unchecked tasks before archiving.
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 - 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.
Phase 4: Report
Archived: .specs/changes/<name>/ → .specs/changes/archive/YYYY-MM-DD-<name>/
Tasks: {N}/{N} complete
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
Related Skills
ahgraber/python-testing
development
VerifiedTrustedCommunity
Use when writing or reviewing tests for Python behavior, contracts, async lifecycles, or reliability paths. Also use when tests are flaky, coupled to implementation details, missing regression coverage, slow to run, or when unclear what tests a change needs. Use for multi-Python version testing (nox) and free-threaded Python thread-safety validation.
3SKILL.mdUpdated Mar 29, 2026
ahgraber/editorial-review
development
VerifiedTrustedCommunity
Use when the user wants rigorous, non-sycophantic editorial feedback on a draft, essay, blog post, or argument through back-and-forth dialogue — pressure-testing thesis, structure, argument, clarity, tone, and evidence. Triggers: "be my sparring partner", "pressure-test this draft", "poke holes in my argument", "is this ready to publish", "sharpen this post", "where is this weak". Not for one-shot copyediting, proofreading, or ghostwriting.
2SKILL.mdUpdated May 26, 2026
ahgraber/synthesize
testing
VerifiedTrustedCommunity
Use when distilling the through-line gist of one or more sources — the spine, argument, tension, or recurring frame running through a set of documents, notes, research, or transcripts, OR across the ideas within a single rich piece — into a few concise paragraphs. Triggers: "synthesize", "what's the through-line/gist", "extract the insight", "pull these together". Not for faithful summary or condensation that covers what a source says, nor for comparisons or catalogs where enumeration is the deliverable.
2SKILL.mdUpdated May 22, 2026
ahgraber/writing-tests
development
VerifiedTrustedCommunity
Use when writing or reviewing tests in any language, or diagnosing a suite that is slow, brittle, or hard to read. Triggers: "write tests", "how should I test this", "what kind of test", "test is flaky/fragile", "should I mock this", "test is hard to read". For Python-specific guidance see `python-testing`.
2SKILL.mdUpdated May 16, 2026