Plan Project

Plan Project

Automate initial project planning: gather requirements, generate planning docs, create SESSION.md, and prepare for Phase 1.

---

Your Task

Follow these steps to take a project from description to ready-to-code state.

0. Check for PROJECT_BRIEF.md (Optional)

**If PROJECT_BRIEF.md exists** in project root or planning/ directory:

ls PROJECT_BRIEF.md planning/PROJECT_BRIEF.md 2>/dev/null

**If found:**

• Read PROJECT_BRIEF.md first
• Extract validated scope, tech stack, and constraints
• Use as context for project-planning skill invocation
• Skip redundant questions (tech stack and scope decisions already validated in brief)

**Note**: PROJECT_BRIEF.md is created by the `/explore-idea` command during pre-planning exploration. It contains research findings and validated decisions that streamline the planning process.

**If not found:**

• Continue normally to step 1
• project-planning skill will handle all requirements gathering

1. Invoke project-planning Skill

**If project description is vague or incomplete**, ask 1-2 clarifying questions first:

• "What's the core functionality? (e.g., task manager, blog, analytics dashboard)"
• "Any specific tech requirements beyond the default stack?"

**Then invoke the project-planning skill** with the project description:

• The skill will handle all clarifying questions (auth, data model, features, scope)
• The skill will generate appropriate planning docs (IMPLEMENTATION_PHASES.md + others as needed)
• Wait for skill to complete and output planning docs

**Note**: Do NOT ask the same questions the skill will ask. Let the skill handle requirements gathering.

2. Verify Planning Docs Exist

Check that these files were created:

• docs/IMPLEMENTATION_PHASES.md (required)
• Other docs as generated (DATABASE_SCHEMA.md, API_ENDPOINTS.md, etc.)

Run:

ls docs/IMPLEMENTATION_PHASES.md

**If IMPLEMENTATION_PHASES.md doesn't exist:**

• Output: "❌ Planning failed. IMPLEMENTATION_PHASES.md not found."
• Output: "The project-planning skill should have created this file. Try running the skill manually."
• Stop here

3. Create SESSION.md

**Read IMPLEMENTATION_PHASES.md** to extract phases:

# Extract project name, phase count, and phase details

**Create SESSION.md** in project root using this template:

# Session State

**Current Phase**: Phase 1
**Current Stage**: Implementation
**Last Checkpoint**: [none yet] ([date])
**Planning Docs**: `docs/IMPLEMENTATION_PHASES.md`[, `docs/DATABASE_SCHEMA.md`][, other docs...]

---

## Phase 1: [Phase Name] 🔄
**Type**: [Type] | **Started**: [date]
**Spec**: `docs/IMPLEMENTATION_PHASES.md#phase-1`

**Progress**:
- [ ] [First task from IMPLEMENTATION_PHASES.md]
- [ ] [Second task]
- [ ] [Third task]

**Next Action**: [Concrete first action from phase tasks]

**Key Files**:
- [List key files from phase]

**Known Issues**: None

## Phase 2: [Phase Name] ⏸️
**Spec**: `docs/IMPLEMENTATION_PHASES.md#phase-