task-planninglisted

# Task Planning Skill Produces exactly one active `TASK_PLAN.md` (template: `templates/task/TASK_PLAN.md`) from either a prepared plan or a plain description. The plan is repository-aware: every stated path and fact is verified or explicitly marked for verification. ## When to Use - The `start` action, with either input type. - Resuming a `planning`-stage workflow. ## Inputs - Raw user input (ready plan or description). - `PROJECT_CONTEXT.md`, `FEATURE_CHANGELOG.md` (searched via the feature-changelog skill **before** writing the plan). - Detection facts (`bin/frappe-workflow detect --json`), current Git state. ## Outputs - `TASK_PLAN.md` passing `bin/frappe-workflow validate task-plan` ([references/plan-validation.md](references/plan-validation.md)). - Frontmatter filled: deterministic `task_id` (TASK-YYYY-NNN — next number from prior plans/Git history, never reusing a found ID; start at 001 when none found), `task_type`, `status: planned`, app/bench/site facts, `suggested_branch`, `related_features`. ## Procedure 1. **Active-task rule:** an unfinished task is never silently replaced — the frappe-task router enforces this before delegating here. 2. Feature search first ([existing-feature-analysis.md](references/existing-feature-analysis.md)). 3. For ready plans: treat as input, not truth — verify every path, add missing technical/validation/security/migration steps, convert to the standard format; report every correction made. 4. For descriptio