sirius-cc-wu/archive-artifacts
skills/archive-artifacts/SKILL.md
Reports archive candidates and safely archives closed slices, including feature/subfeature scoped summarize-and-archive flows.
$ install --global
skillsauthnpx skillsauth add sirius-cc-wu/sirius-skills archive-artifactsInstall 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: May 7, 2026, 5:15 AM108.2s4 files scanned
SKILL.md
- name:
- archive-artifacts
- description:
- Reports archive candidates and safely archives closed slices, including feature/subfeature scoped summarize-and-archive flows.
Archive Artifacts
Use this skill when a maintainer needs an explicit archival step that preserves durable history without broad cleanup side effects.
Responsibilities
- Discover archive candidates across proposals, features, subfeatures, and closed slices.
- Keep candidate reporting read-only by default.
- Archive one closed execution slice explicitly through the execution owner helper.
- Summarize closed slices for one feature or subfeature into
system-design.mdbefore archiving them.
Preferred Input
- no arguments for archive candidate discovery
- optional artifact-type filtering
--artifact-type slice --artifact-id <id> --applyfor one closed-slice archival--artifact-type feature --artifact-id <feature-slug> --applyto summarize and archive all closed planned slices for one feature--artifact-type subfeature --artifact-id <subfeature-id-or-path> --applyto summarize and archive all closed planned slices for one subfeature
Tooling
# Report archive candidates
python3 skills/archive-artifacts/scripts/archive_artifacts.py
# Filter to one artifact type
python3 skills/archive-artifacts/scripts/archive_artifacts.py --artifact-type proposal
# Archive one closed slice
python3 skills/archive-artifacts/scripts/archive_artifacts.py \
--artifact-type slice \
--artifact-id rpt-artifact-state-report \
--apply
# Summarize and archive closed slices for one feature
python3 skills/archive-artifacts/scripts/archive_artifacts.py \
--artifact-type feature \
--artifact-id execution-workflow \
--apply
# Summarize and archive closed slices for one subfeature
python3 skills/archive-artifacts/scripts/archive_artifacts.py \
--artifact-type subfeature \
--artifact-id audit-artifacts \
--apply
# Optional: preserve existing structural class/component diagrams too
python3 skills/archive-artifacts/scripts/archive_artifacts.py \
--artifact-type subfeature \
--artifact-id audit-artifacts \
--apply \
--include-structural-diagrams
# Emit machine-readable output
python3 skills/archive-artifacts/scripts/archive_artifacts.py --json
Output
- default: human-readable candidate summary
--json: structured candidates and optional apply outcome
Exit behavior:
0when the archive command succeeds2for unsupported or invalid apply requests
Guardrails
- Keep candidate discovery read-only.
- Delegate slice archival to the execution owner helper instead of moving slice folders directly here.
- For feature and subfeature apply mode, summarize slice history into
system-design.mdbefore archiving the targeted closed slices. - Keep structural-diagram carry-forward opt-in and limited to preserving
existing class/component-style PlantUML from blueprint or canonical
system-design.md; do not synthesize new diagrams during archive. - Keep archived slice summaries self-contained inside
system-design.md; do not rely on source or archive path bullets to explain the result. - Keep archival explicit and scoped; do not bulk archive across unrelated features by default.
- Do not treat archival as the default next step when the current user request
is a new fix, regression, or follow-on capability for the same shipped
feature; route that case back to
guide-planning/add-subfeatureunless the user explicitly asked to archive anyway.
Related Skills
sirius-cc-wu/ship-worktree
tools
VerifiedTrustedCommunity
Create or resume a dedicated git worktree for one feature or subfeature, drive `ship` inside that worktree, and hand the finished branch back as a pull request to the original branch.
4SKILL.mdUpdated May 6, 2026
sirius-cc-wu/reconcile-execution
testing
VerifiedTrustedCommunity
Reviews one completed feature or subfeature against final implementation and slice artifacts, then records a durable reconciliation block before archive.
4SKILL.mdUpdated May 6, 2026
sirius-cc-wu/governance-update
development
VerifiedTrustedCommunity
Tightens durable repo-level rules in AGENTS.md and adjacent governance surfaces when repeated drift reveals a policy gap.
4SKILL.mdUpdated Apr 29, 2026
sirius-cc-wu/ship
data-ai
VerifiedTrustedCommunity
Resolves one reviewed feature or subfeature backlog into remaining planned slices and routes each active slice to the next owning execution step with one commit per completed slice.
4SKILL.mdUpdated Apr 22, 2026