Plan

## Your mission
<task>
$ARGUMENTS
</task>

## Pre-Creation Check (Active vs Suggested Plan Detection)

Before delegating to plan subcommands, check plan state:

1. **Check `$CK_ACTIVE_PLAN` env var (explicitly active):**
   - If set and points to valid directory:
     - Ask user: "Active plan found: {path}. Continue with this? [Y/n]"
     - If Y (default): Pass existing plan path to subcommand, skip folder creation
     - If n: Proceed to create new plan

2. **Check `$CK_SUGGESTED_PLAN` env var (branch-matched, NOT active):**
   - If set: Inform user "Found suggested plan from branch: {path}"
   - This is a hint only - do NOT auto-use it
   - Ask user if they want to activate it or create new plan

3. **If neither is set:** Proceed to create new plan (subcommand handles)

## Workflow
- Analyze the given task and use `AskUserQuestion` tool to ask for more details if needed.
- Decide to use `/plan:fast` or `/plan:hard` SlashCommands based on the complexity.
- Execute SlashCommand: `/plan:fast <detailed-instructions-prompt>` or `/plan:hard <detailed-instructions-prompt>`
- Activate `planning` skill.
- Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the task in detail based on the provided task description.

## Important Notes
**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:** Ensure token efficiency while maintaining high quality.
**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
**IMPORTANT**: **Do not** start implementing.