SKILL.md
<skillcontext> <skilldir>skills/prd-to-slices</skilldir> <workspacedir>/Users/tothemoon/Dev/code-forge/knowledge-wiki-system</workspace_dir>
<pathpolicy> Relative file references in this SKILL.md normally resolve from skilldir when they exist there. Plain workspace commands like git status and bun test usually run in the workspace unless instructed otherwise. Use $PISKILLDIR/path for explicit bundled skill files. Use $PIWORKSPACE/path for explicit workspace/project files. </pathpolicy> </skill_context>
Wiki/Forge session context
Resolve vault via KNOWLEDGEVAULTROOT or wiki config --effective --repo <path>. Do not create durable project memory markdown inside the code repo unless the repo itself is the configured vault. Forge-tracked use: obey the active Forge phase packet, its required skills, artifact owner, and allowed writes. Standalone use: route durable memory through Wiki under ${KNOWLEDGEVAULTROOT}/projects/<project>/.
PRD to Slices
Break a plan into independently grabbable vertical slices using tracer bullets.
Process
- Gather context from the conversation or referenced artifact.
- Explore code if needed; use domain glossary vocabulary and respect ADRs.
- Draft thin vertical slices that cut through every required integration layer.
- Mark slices HITL only when human input is truly needed; otherwise prefer AFK.
- Each slice delivers a narrow but COMPLETE path through the system.
- Prefer many thin slices over few thick ones.
- Ask the user whether granularity, dependencies, and HITL/AFK labels are correct.
- Publish approved slices through Forge in dependency order.
Slice template
- Parent: feature or PRD reference.
- What to build: concise end-to-end behavior, not layer-by-layer tasks.
- Acceptance criteria.
- Blocked by: blockers or
None - can start immediately.
Avoid file paths and snippets unless a prototype artifact encodes a decision more precisely than prose.
Phase: plan (step 3 of 3)
This skill is loaded after /write-a-prd publishes the PRD (step 2).
Break the PRD into thin vertical tracer-bullet slices. Each slice cuts through every required integration layer and delivers a narrow but complete path through the system.
After slices are published, the plan phase is complete. Run wiki forge next to start implementation.
Forge integration
Load this skill when the phase packet lists prd-to-slices. Publish slices with wiki forge plan <project> <feature-name> [--repo <path>]. Forge status is workflow truth. Checkpoint/maintain are Health-owned freshness and repair truth. After slicing completes: return to /forge — run wiki forge next to advance.