Skill: /plan-feature

Usage

/plan-feature "{task_description}"

Examples:

/plan-feature "add product filtering by category on the listing page"
/plan-feature "fix cart total not updating when quantity is changed"
/plan-feature "refactor order service to extract coupon logic"

Prerequisites

• /read-references must have been executed in this session
• If reference context is missing, invoke /read-references first

Mode: READ-ONLY

In this step you MAY:

• Read any file on disk
• Run grep, find, cat to explore the codebase
• Ask the lead clarifying questions

You MUST NOT:

• Write, edit, or delete any file
• Run migrations, artisan commands, or npm scripts
• Make any git operations

Planning Process

Phase 1: Task Analysis

Restate the task in your own words to confirm understanding:

TASK UNDERSTOOD:
Type        : feature | update | fix
Description : {restatement in 1–2 sentences}
Technology  : laravel | react | react-native | frontend | mixed
Complexity  : low | medium | high (justify in 1 sentence)

If the task is ambiguous, ask ONE clarifying question and wait for the answer before proceeding.

Phase 2: Impact Analysis

Using the reference files and codebase exploration, identify every area affected by this task:

IMPACT ANALYSIS:
─────────────────────────────────────────
Database changes?    : yes / no
  If yes → tables: [list], type: migration / seed / both

Backend changes?     : yes / no
  If yes → routes / controllers / services / repositories / models

Frontend changes?    : yes / no
  If yes → pages / components / hooks / stores / services

Mobile changes?      : yes / no
  If yes → screens / navigators / services

Config/env changes?  : yes / no
  If yes → [specify files and keys — NEVER commit actual values]
─────────────────────────────────────────

Phase 3: Implementation Plan

List every file to be created or modified. For each file:

📝 CREATE  src/services/ProductFilterService.php
   → New service class. Methods: filter(array $criteria): Builder
   → Called by: ProductController@index

✏️  MODIFY  app/Http/Controllers/ProductController.php
   → Inject ProductFilterService. Update index() to accept filter params.
   → No other methods touched.

✏️  MODIFY  references/{relevant_map}.md                 ← ALWAYS include the affected reference map(s)
   → Reflect the implementation so future tasks start from fresh project maps.

Format each entry as:

{icon} {CREATE|MODIFY|DELETE}  {file_path}
   → {what changes and why, 1–2 lines}
   → {dependencies or callers, if relevant}

Icons: 📝 = new file, ✏️ = modify, 🗑️ = delete

Rules for the file list:

• Always include references/{relevant_map}.md as a MODIFY entry
• List files in dependency order (models before services before controllers)
• If a migration is needed, list it FIRST
• Never include vendor/, node_modules/, .env files

Phase 4: Risk Assessment

RISK ASSESSMENT:
──────────────────────────────────────
Overall risk    : low | medium | high
Breaking change : yes / no
  If yes → describe what breaks and what callers are affected

Database risk   : none | additive | destructive
  If destructive → requires lead sign-off before migration runs

Auth/Security   : affected / not affected
  If affected → flag to security-reviewer

Performance     : no impact | minor impact | significant impact
  If significant → describe expected impact
──────────────────────────────────────

Phase 5: Approval Request

──────────────────────────────────────────────────────────────
  PLAN READY — AWAITING APPROVAL
──────────────────────────────────────────────────────────────
Files to create : {count}
Files to modify : {count}
Files to delete : {count}
Risk level      : {level}

Respond with:
  ✅  approve     — proceed to /implement-plan
  ✏️   revise {N}  — clarify or change item N in the plan
  ❌  reject      — cancel and explain why
──────────────────────────────────────────────────────────────

Do NOT proceed to implementation until the lead explicitly approves.