// This skill should be used when the user asks "what is a slice", "slice phases", "how do slices work", "slice workflow", or needs to understand the slice delivery lifecycle. Covers four phases: requirements, design, implementation, and completion with phase gates and review.
| name | slice-lifecycle |
| description | This skill should be used when the user asks "what is a slice", "slice phases", "how do slices work", "slice workflow", or needs to understand the slice delivery lifecycle. Covers four phases: requirements, design, implementation, and completion with phase gates and review. |
Overview of Forge slice lifecycle. Slices are the delivery phase — designing, implementing, and shipping focused deliverables.
Slice: Focused deliverable with clear scope and timeline.
Input: Requirements from effort (or standalone).
Output: Working software shipped to users.
Duration: Days to weeks (time-boxed).
Location: .forge-context/slices/YYYYMM-{slug}/
Example slices:
Command: /forge:requirements
Actions:
Output:
requirements.md with:
Review: Create PR for area owner review and approval
Command: /forge:design
Actions:
Output:
design.md with:
tasks.md structure preparedReview: Create PR for area owner review and approval
Command: /forge:start-task
Actions:
Output:
tasks.md updated with statusReview: Per-task code review
Command: /forge:phase-complete
Actions:
Output:
Review: Final completion PR
.forge-context/slices/YYYYMM-{slug}/
requirements.md # What we're building
design.md # How we're building it
tasks.md # Task breakdown + status
decisions.md # ADRs
checklist.md # Phase tracking
artifacts/ # Supporting materials
retrospective-notes.md
Slice status is tracked in tasks.md (per-task status) and
checklist.md (phase completion tracking with dates).
tasks.md Snapshot:
| Task | Description | Status | PR |
|------|-------------|--------|-----|
| T1 | Add auth model | ✅ | #42 |
| T2 | Add auth API | 🔄 | - |
Requirements → Design:
Design → Implementation:
Implementation → Complete:
Phase gates: Each phase requires PR approval before next phase begins.
Create slice when:
Defer to effort when:
1. /forge:work new
2. /forge:requirements
3. /forge:design
4. /forge:start-task (per task)
5. /forge:phase-complete
1. /forge:work new (from effort candidate)
2. /forge:requirements (refine from effort)
3. /forge:design
4. /forge:start-task (per task)
5. /forge:phase-complete
/forge:work new — Initialize slice/forge:requirements — Requirements phase/forge:design — Design phase/forge:start-task — Implement task/forge:phase-complete — Complete phase/forge:process-pr-discussions — Process PR feedbackrequirements-gatherer — Requirements phasedesigner — Design phaseimplementation-worker — Implement taskscode-reviewer — Review PRsphase-completer — Phase completion| Phase | Command | Output | Review |
|---|---|---|---|
| Requirements | /forge:requirements | requirements.md | Approval |
| Design | /forge:design | design.md, tasks.md | Approval |
| Implementation | /forge:start-task | Code PRs | Per-task |
| Complete | /forge:phase-complete | Phase PR | Approval |
Key principles:
Create and manage Flox development environments. Use when setting up a project environment during /forge:init, when a user asks to add a Flox environment, or when detecting and installing project dependencies. Covers flox init, search, install, manifest basics, and language-specific patterns. For advanced topics (services, builds, CUDA, layering, containers), suggest the full flox plugin.
This skill should be used when "restructuring commits", "organizing PR history", "making commits reviewable", or planning how to split work into atomic commits. The intellectual foundation for /reviewable. Do not use for writing commit messages (see git workflow guideline).
This skill should be used when the user redirects, corrects, or refines agent output — "no, actually", "that's not right", "you missed something". Captures correction moments to improve Forge workflows over time. Always active during feature work; log corrections as they occur.
This skill should be used when the user asks "what is an effort", "effort phases", "how do efforts work", "effort vs slice", or needs to understand the effort lifecycle. Covers the five phases: initialize, story capture, requirements, slice identification, and slice spawning.
Surface Forge plugin documentation when users ask "how does forge work", "forge help", "what commands are available", or need guidance on workflows, commands, or concepts. Use for onboarding, command reference, or workflow overview questions.
This skill should be used when a command needs the full implement-and-review cycle — spawning an implementation worker, running a code review gate, and making a post-review decision. Used by /forge:start-task and /implement. Do not use for review-only or implementation-only workflows.