---
name: craft-lifecycle
description: "Use when the user has an active craft session (.craft/state.json exists), discusses software development lifecycle phases, or mentions ideation, planning, validation, deployment workflows, or shipping features."
---

# Craft Lifecycle Skill

Use when the user has an active craft session (.craft/state.json exists), discusses software development lifecycle phases, or mentions ideation, planning, validation, deployment workflows, or shipping features.

## Behavior

When this skill activates, you have awareness of the craft lifecycle system and can guide the user through it.

### If `.craft/state.json` exists

Read the state file and provide context-aware assistance:

1. **Report current state** — Tell the user which phase they're in and what progress has been made
2. **Suggest next action** — Based on the current phase, recommend the appropriate command:
   - `ideation` in progress → Guide them through ideation or suggest completing it
   - `ideation` complete → Suggest `/craft:plan`
   - `planning` in progress → Guide them through planning decisions
   - `planning` complete → Suggest `/craft:build`
   - `build` in progress → Help with implementation, check task progress
   - `build` complete → Suggest `/craft:validate`
   - `validate` in progress → Help interpret findings
   - `validate` complete → Suggest `/craft:ship`
   - `ship` in progress → Help with deployment prep
   - All complete → Congratulate and summarize artifacts

3. **Provide context** — When the user asks about the feature being crafted, pull relevant info from:
   - `docs/craft/requirements.md` — What's being built
   - `docs/craft/architecture.md` — How it's designed
   - `.craft/planning/tasks.md` — What tasks remain
   - `.craft/validation/review-notes.md` — What issues were found

### If no active session

When the user discusses lifecycle topics without an active session:

1. **Introduce craft** — Briefly explain what `/craft:craft` does and how it can help
2. **Suggest getting started** — Recommend `/craft:craft` for the full lifecycle or individual phase commands for specific needs:
   - Have an idea to explore? → `/craft:ideate`
   - Know what to build, need a plan? → `/craft:plan`
   - Have a plan, ready to build? → `/craft:build`
   - Code written, need validation? → `/craft:validate`
   - Ready to deploy? → `/craft:ship`
   - Want the full journey? → `/craft:craft`

### Reference materials

For detailed guidance, load from the `references/` directory:
- `references/phase-guidelines.md` — Best practices per phase
- `references/deploy-platforms.md` — Platform-specific deployment patterns

Load these on demand when the user needs detailed phase guidance or deployment-specific information.