archive-artifacts

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

1. Discover archive candidates across proposals, features, subfeatures, and closed slices.
2. Keep candidate reporting read-only by default.
3. Archive one closed execution slice explicitly through the execution owner helper.
4. Summarize closed slices for one feature or subfeature into system-design.md before archiving them.
5. Remove or archive the corresponding slice-planning.md and slice-traceability.md artifacts after the summary is captured.

Preferred Input

• no arguments for archive candidate discovery
• optional artifact-type filtering
• --artifact-type slice --artifact-id <id> --apply for one closed-slice archival
• --artifact-type feature --artifact-id <feature-slug> --apply to summarize and archive all closed planned slices for one feature
• --artifact-type subfeature --artifact-id <subfeature-id-or-path> --apply to summarize and archive all closed planned slices for one subfeature

Tooling

# Report archive candidates
sirius archive-artifacts

# Filter to one artifact type
sirius archive-artifacts --artifact-type proposal

# Archive one closed slice
sirius archive-artifacts \
  --artifact-type slice \
  --artifact-id rpt-artifact-state-report \
  --apply

# Summarize and archive closed slices for one feature
sirius archive-artifacts \
  --artifact-type feature \
  --artifact-id execution-workflow \
  --apply

# Summarize and archive closed slices for one subfeature
sirius archive-artifacts \
  --artifact-type subfeature \
  --artifact-id audit-artifacts \
  --apply

# Optional: preserve existing structural class/component diagrams too
sirius archive-artifacts \
  --artifact-type subfeature \
  --artifact-id audit-artifacts \
  --apply \
  --include-structural-diagrams

# Emit machine-readable output
sirius archive-artifacts --json

Output

• default: human-readable candidate summary
• --json: structured candidates and optional apply outcome

Exit behavior:

• 0 when the archive command succeeds
• 2 for 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.md before archiving the targeted closed slices.
• After summarizing, clean up the targeted slice-planning.md and slice-traceability.md files so the archival set is complete.
• 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-subfeature unless the user explicitly asked to archive anyway.