sirius-cc-wu/execute-all-slices
skills/execute-all-slices/SKILL.md
Resolves one reviewed feature or subfeature backlog into remaining planned slices and, in later slices, will execute them sequentially with one commit per completed slice.
$ install --global
skillsauthnpx skillsauth add sirius-cc-wu/sirius-skills execute-all-slicesInstall 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 19, 2026, 2:36 AM6.0s3 files scanned
SKILL.md
- name:
- execute-all-slices
- description:
- Resolves one reviewed feature or subfeature backlog into remaining planned slices and, in later slices, will execute them sequentially with one commit per completed slice.
Execute All Slices
Use this skill when a maintainer wants to work through all planned slices for one reviewed and committed feature or subfeature.
Responsibilities
The first slice of this capability establishes durable scope and backlog resolution:
- Resolve exactly one feature or subfeature planning packet.
- Read its planned slices and dependency order from planning artifacts.
- Compare planned slices with execution-slice lineage and closure state.
- Report which planned slices are completed, active, ready next, or blocked.
The second slice adds conservative sequential orchestration:
- Bootstrap exactly one next-ready execution slice when no mapped slice is already active.
- Record the bootstrapped execution slice ID back into
slice-traceability.md. - Hand the active slice back to the existing execution owners.
The third slice adds stop/resume semantics:
- Resume an already-active mapped slice instead of creating a second one.
- Recompute progress from closed slices, active slices, and dependencies without a batch-only progress file.
- Stop explicitly when unfinished planned slices remain but none are ready.
The fourth slice adds per-slice commit checkpoints:
- Refuse to bootstrap the next slice while the repository still has uncommitted changes after a completed mapped slice.
- Hand that checkpoint back to the existing
commitowner instead of silently absorbing more work into the next slice.
Preferred Input
- a feature slug, subfeature slug, or planning packet path
- optional
--scope <path>when nested planning scopes are ambiguous
Tooling
python3 skills/execute-all-slices/scripts/execute_all_slices.py <target>
python3 skills/execute-all-slices/scripts/execute_all_slices.py <target> --json
python3 skills/execute-all-slices/scripts/execute_all_slices.py <target> --bootstrap-next
python3 skills/execute-all-slices/scripts/execute_all_slices.py <target> --resume
python3 skills/execute-all-slices/scripts/execute_all_slices.py <target> --scope apps/payments
Guardrails
- Resolve exactly one planning scope; do not guess across ambiguous scopes.
- Do not create or mutate execution slices during the first slice of this
capability beyond explicit
--bootstrap-nextorchestration. - Treat planning and execution registries as the source of truth for backlog and completion state.
- Refuse batch bootstrap when
slice-traceability.mdgroups multiple planned slices into one row; the mapping is ambiguous and should be split first. - Stop when unfinished planned slices remain but no mapped slice is active and no dependency-ready slice exists.
- Require a clean worktree before continuing past a completed mapped slice so one commit still represents one completed execution slice.
- Keep one-slice execution ownership in the existing
slice,guide-execution,review-execution,close-slice, andcommitskills.
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