Ck:plan

Planning

Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.

Default (No Arguments)

If invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, ask the user to choose an operation:

Present options with header "Planning Operation", question "What would you like to do?".

Workflow Modes

Default: --auto (analyze task complexity and auto-pick mode).

Add --no-tasks to skip task hydration in any mode.

Load: references/workflow-modes.md for auto-detection logic, per-mode workflows, context reminders.

When to Use

• Planning new feature implementations
• Architecting system designs
• Evaluating technical approaches
• Creating implementation roadmaps
• Breaking down complex requirements

Core Responsibilities & Rules

Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.

1. Research & Analysis

Load: references/research-phase.md Skip if: Fast mode or provided with researcher reports

2. Codebase Understanding

Load: references/codebase-understanding.md Skip if: Provided with scout reports

3. Solution Design

Load: references/solution-design.md

4. Plan Creation & Organization

Load: references/plan-organization.md

5. Task Breakdown & Output Standards

Load: references/output-standards.md

Workflow Process

1. Pre-Creation Check → Check Plan Context for active/suggested/none
2. Mode Detection → Auto-detect or use explicit flag (see workflow-modes.md)
3. Research Phase → Spawn researchers (skip in fast mode)
4. Codebase Analysis → Read docs, scout if needed
5. Plan Documentation → Write comprehensive plan via planner subagent
6. Red Team Review → Use Skill tool: plan:red-team {plan-path} (hard/parallel/two modes)
7. Post-Plan Validation → Use Skill tool: plan:validate {plan-path} (hard/parallel/two modes)
8. Hydrate Tasks → Create tracked tasks from phases when task tools exist (default on, --no-tasks to skip)
9. Context Reminder → Output cook command with absolute path (MANDATORY)

Output Requirements

• DO NOT implement code - only create plans
• Respond with plan file path and summary
• Ensure self-contained plans with necessary context
• Include code snippets/pseudocode when clarifying
• Fully respect the workflow rules in ./.codex/rules/development-rules.md

Task Management

Plan files = persistent. Tasks = session-scoped. Hydration bridges the gap.

Default: Auto-hydrate tasks after plan files are written. Skip with --no-tasks. 3-Task Rule: <3 phases → skip task creation.

Load: references/task-management.md for hydration pattern, task creation patterns, cook handoff protocol.

Hydration Workflow

1. Write plan.md + phase files (persistent layer)
2. Create one tracked task per phase with dependency chain when task tools exist
3. Create tracked tasks for critical/high-risk steps within phases when useful
4. Metadata: phase, priority, effort, planDir, phaseFile
5. Cook picks up existing tasks when available or re-hydrates from plan files in a new session

Active Plan State

Check ## Plan Context injected by hooks:

• "Plan: {path}" → Active plan. Ask "Continue? [Y/n]"
• "Suggested: {path}" → Branch hint only. Ask if activate or create new.
• "Plan: none" → Create new using Plan dir: from ## Naming

After creating plan: node .codex/scripts/set-active-plan.cjs {plan-dir} Reports: Active plans → plan-specific path. Suggested → default path.

Important

DO NOT create plans or reports in USER directory. ALWAYS create plans or reports under the configured Plan dir: / Reports: paths from the injected ## Naming and ## Paths context. For umbrella repositories, this may point at the umbrella root even when the current work context is a child repo.

Subcommands

Quality Standards

• Thorough and specific, consider long-term maintainability
• Research thoroughly when uncertain
• Address security and performance concerns
• Detailed enough for junior developers
• Validate against existing codebase patterns

Remember: Plan quality determines implementation success. Be comprehensive and consider all solution aspects.