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.
From forgenpx claudepluginhub flox/forge-plugin --plugin forgeThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
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: