sirius-cc-wu/close-slice
skills/close-slice/SKILL.md
Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.
$ install --global
skillsauthnpx skillsauth add sirius-cc-wu/sirius-skills close-sliceInstall 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 8, 2026, 4:54 AM209.1s12 files scanned
SKILL.md
- name:
- close-slice
- description:
- Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.
Close Slice
Use this skill when implementation is complete and you want to close an execution slice cleanly.
Responsibilities
- Resolve the target slice through
guide-execution. - Validate that the slice is ready to close.
- Close the slice without deleting the original artifacts.
- Optionally record explicit invalidation or supersession relations as part of closure.
Source of Truth Rules
- Keep the original slice artifacts intact.
close-slicerecords closure only; any later cleanup or archival is a separate explicit maintenance step. - Treat
<slice_dir>/README.md,<slice_dir>/registry.json, and<slice_path>/.slice-meta.jsonas the canonical closure records.
Artifact Ownership
close-slice owns closure metadata updates and relation-bearing slice closure.
After closure, it invokes the shared workflow_state.owner_completion hook so
feature and subfeature completion can be reconciled from traceability plus
closed execution slices.
guide-execution should route into closure only after execution review is complete; it should not replace close-slice by mutating closure state directly outside normal registry/status tooling.
Workflow
- Resolve the target slice explicitly, or use the active slice.
- Run
manage_execution.py validate-slice. - If the slice is not already
closed, close it through tooling. - Run shared owner-completion reconciliation for planning owners linked to the closed slice.
- If relation-bearing closure is requested:
- record explicit slice relations such as
supersedesorreplaces_partially - require explicit impact confirmation unless forced
- run relation auditing through the execution registry tooling
- record explicit slice relations such as
- Return the closed slice outcome, owner-sync results, and the retained source artifacts.
Tooling
# Close the active slice
python3 <path-to-close-slice>/scripts/close_slice.py
# Close a slice while explicitly confirming that it supersedes an older one
python3 <path-to-close-slice>/scripts/close_slice.py --slice "<slice-id-or-path>" --relate supersedes "<old-slice-id-or-path>" --confirm-impact
# Close a slice with a partial replacement relation scoped to one story/requirement
python3 <path-to-close-slice>/scripts/close_slice.py --slice "<slice-id-or-path>" --relate replaces_partially "<old-slice-id-or-path>" --story-title "Story 2 - Legacy flow" --requirement-id FR-002 --selector "legacy checkout path" --confirm-impact
# Output JSON for downstream tooling
python3 <path-to-close-slice>/scripts/close_slice.py --json
Use --confirm-impact when closure also changes the semantic validity of older execution slices. Use --force only for deliberate repair when the slice lifecycle is temporarily inconsistent and you have already verified the intent with the user.
If a repository later wants to archive or prune closed slices, treat that as a separate explicit maintenance workflow rather than part of slice closure.
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