Workflow

Workflow

Interactive guide to the Claude Skills Workflow: 5 commands for complete project lifecycle automation.

---

Your Task

Help the user understand and use the 5-command workflow system by providing interactive guidance based on their current context.

Overview: The 5 Commands

Display this summary first:

═══════════════════════════════════════════════
   CLAUDE SKILLS WORKFLOW - 5 COMMANDS
═══════════════════════════════════════════════

1. /explore-idea     → Research & validate ideas (PRE-planning)
2. /plan-project     → Generate planning docs (NEW projects)
3. /wrap-session     → Checkpoint progress (end of session)
4. /continue-session   → Load context (start of session)
5. /plan-feature     → Add features (EXISTING projects)

Complete Workflow:
Idea → /explore-idea → /plan-project → Work → /wrap-session → /continue-session (cycle)

Quick Workflow (clear requirements):
Idea → /plan-project → Work → /wrap-session → /continue-session (cycle)

Feature Addition:
/plan-feature → Work → /wrap-session → /continue-session (cycle)

═══════════════════════════════════════════════

Step 1: Ask User's Context

Ask the user what they're trying to do:

What are you trying to do?

1. Explore a new project idea (not sure about approach yet)
2. Plan a new project (I know what I want)
3. Add a feature to existing project
4. Wrap my current session (context getting full)
5. Resume work on a project
6. Show me the complete workflow guide

Your choice (1-6):

Step 2: Provide Context-Aware Guidance

Based on the user's choice, provide specific guidance:

Choice 1: Explore New Idea

═══════════════════════════════════════════════
   EXPLORING A NEW IDEA
═══════════════════════════════════════════════

You should use: /explore-idea

What it does:
• Free-flowing conversation (not rigid questionnaire)
• Heavy research (approaches, examples, alternatives)
• Validates tech stack and feasibility
• Challenges assumptions, prevents scope creep
• Sometimes recommends NOT building
• Creates PROJECT_BRIEF.md with validated decisions

When to use:
✅ Rough idea but not validated approach
✅ Multiple tech options, unsure which fits
✅ Want research/validation before committing

When to skip:
❌ Crystal-clear requirements (use /plan-project)

Output: PROJECT_BRIEF.md

Next step: /plan-project (reads the brief automatically)

Time saved: 10-15 minutes

═══════════════════════════════════════════════

Ready to run /explore-idea? (y/n)

If yes: Execute `/explore-idea`

---

Choice 2: Plan New Project

═══════════════════════════════════════════════
   PLANNING A NEW PROJECT
═══════════════════════════════════════════════

You should use: /plan-project

What it does:
• Checks for PROJECT_BRIEF.md (from /explore-idea)
• Invokes project-planning skill
• Generates IMPLEMENTATION_PHASES.md
• Creates SESSION.md automatically
• Creates git commit with planning docs
• Asks permission to start Phase 1

Prerequisites:
• Git reposito