---
description: Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
---

# Plan Command

This command invokes the **planner** agent to create a comprehensive implementation plan before writing any code.

## What This Command Does

1. **Restate Requirements** - Clarify what needs to be built
2. **Identify Risks** - Surface potential issues and blockers
3. **Create Step Plan** - Break down implementation into phases
4. **Wait for Confirmation** - MUST receive user approval before proceeding

## When to Use

Use `/plan` when:

- Starting a new feature
- Making significant architectural changes
- Working on complex refactoring
- Multiple files/components will be affected
- Requirements are unclear or ambiguous

## How It Works

The planner agent will:

1. **Analyze the request** and restate requirements in clear terms
2. **Break down into phases** with specific, actionable steps
3. **Identify dependencies** between components
4. **Assess risks** and potential blockers
5. **Estimate complexity** (High/Medium/Low)
6. **Present the plan** and WAIT for your explicit confirmation

## Example Usage

```
User: /plan Add a FULL_PAGE master-data module for vehicle types, same as example/full-page

Agent (planner):
# Implementation Plan: Vehicle Types FULL_PAGE module

## Requirements Restatement
- New authenticated module under apps/web
- Index, form (create/edit/duplicate), and detail pages
- Copy example/full-page layout and wiring

## Implementation Phases

### Phase 1: Domain + data
- ModuleConfigEntity, entity, Zod validator (createFullPageSchema pattern)
- Remote data service via apiClient + CommonRemoteDataServices
- Transformer DTO ↔ entity

### Phase 2: Presentation
- presentation/factory with EnterpriseModuleProvider + registerModuleNamespace
- Index / form / detail pages using Enterprise* providers
- Field* form fields and detail-layout skill
- Menu + lazy route registration

### Phase 3: Tests
- Vitest for validator and transformer
- Browser-verify index → form → detail

## Dependencies
- @repo/ui foundations and form fields
- @repo/core-api CommonRemoteDataServices
- Backend API already exposing the resource (out of scope)

## Risks
- MEDIUM: i18n namespace mismatch
- LOW: Copying the sample and leaving EXAMPLE_FULL_PAGE keys

## Estimated Complexity: MEDIUM

**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify)
```

## Important Notes

**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response.

If you want changes, respond with:

- "modify: [your changes]"
- "different approach: [alternative]"
- "skip phase 2 and do phase 3 first"

## Integration with Other Commands

After planning:

- Use `/tdd` to implement with test-driven development
- Use `/build-and-fix` if build errors occur
- Use `/code-review` to review completed implementation

## Related Agents

This command invokes the `planner` agent located at:
`.cursor/agents/planner.md`