ck-plan-fast

Prompt file imported from CTNone/Cokit-Edit (.github/prompts/ck-plan-fast.prompt.md). Fill in {{input}} before use. Copyright stays with the author.

Variant Notice

IMPORTANT — Read before proceeding. ck-plan-fast is an internal mode for quick planning without research — it is meant to be selected automatically by AI when you run /ck-plan. You don't need to call this directly. Just use /ck-plan and AI will pick the right mode for you. Before executing, you MUST output the following message exactly as written and wait for user response:

Variant Notice

ck-plan-fast is an internal mode for quick planning without research — it is meant to be selected automatically by AI when you run /ck-plan. You don't need to call this directly. Just use /ck-plan and AI will pick the right mode for you.

Do you want to continue anyway, or switch to /ck-plan? [Continue / Switch to /ck-plan]

Only proceed if user explicitly confirms Continue. If user chooses "Switch to /ck-plan", run immediately — do NOT ask user to re-enter their input.

Think. Activate planning skill.

Your mission

Pre-Creation Check (Active vs Suggested Plan)

Check the ## Plan Context section in the injected context:

• If "Plan:" shows a path → Active plan exists. Ask user: "Continue with this? [Y/n]"
• If "Suggested:" shows a path → Branch-matched hint only. Ask if they want to activate or create new.
• If "Plan: none" → Create new plan using naming from ## Naming section.

Workflow

Use planner agent to:

1. If creating new: Create directory using Plan dir: from ## Naming section, then run node $HOME/.copilot/scripts/set-active-plan.cjs {plan-dir} If reusing: Use the active plan path from Plan Context. Make sure you pass the directory path to every agent during the process.
2. Follow strictly to the "Plan Creation & Organization" rules of planning skill.
3. Analyze the codebase by reading codebase-summary.md, code-standards.md, system-architecture.md and project-overview-pdr.md file.
4. Gathers all information and create an implementation plan of this task.
5. Ask user to review the plan.

Context Reminder (MANDATORY)

IMPORTANT: After plan creation, you MUST remind the user:

Best Practice: Run /clear before implementing to start with fresh context. Then run /cook {plan-path} to begin implementation.

This reminder is NON-NEGOTIABLE - always output it after presenting the plan.

Output Requirements

Plan Directory Structure (use Plan dir: from ## Naming section)

{plan-dir}/
├── reports/
│   ├── XX-report.md
│   └── ...
├── plan.md
├── phase-XX-phase-name-here.md
└── ...

Plan File Specification

• Every plan.md MUST start with YAML frontmatter:

  ---
  title: "{Brief title}"
  description: "{One sentence for card preview}"
  status: pending
  priority: P2
  effort: {sum of phases, e.g., 4h}
  branch: {current git branch}
  tags: [relevant, tags]
  created: {YYYY-MM-DD}
  ---

• Save the overview access point at {plan-dir}/ck-plan.md. Keep it generic, under 80 lines, and list each implementation phase with status and progress plus links to phase files.
• For each phase, create {plan-dir}/phase-XX-phase-name-here.md containing the following sections in order: Context links (reference parent plan, dependencies, docs), Overview (date, description, priority, implementation status, review status), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps.

Important Notes

• IMPORTANT: Ensure token consumption efficiency while maintaining high quality.
• IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
• IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
• IMPORTANT: In reports, list any unresolved questions at the end, if any.
• IMPORTANT: Do not start implementing.

Suggested Next Steps