#What it does

The /plan skill creates a detailed implementation plan before writing any code. It analyzes the codebase, considers architecture trade-offs, and presents a step-by-step plan for your approval.

#How to use

/plan Add OAuth login with GitHub and Google

#What you get

1. Context analysis — Current codebase state, relevant files, patterns
2. Architecture decisions — Technology choices with rationale
3. File plan — Exactly which files to create, modify, or delete
4. Build phases — Ordered steps with dependencies
5. Verification — How to test the implementation

#Key feature

The plan waits for your confirmation before executing. You can:

• Approve and start building
• Request changes to the plan
• Ask questions about specific decisions
• Reject and try a different approach

#When to use

• Before any non-trivial feature (more than 2-3 files)
• When you want to understand the approach before committing
• When coordinating with team members on architecture
• Before refactoring that touches many files