plan-tasklisted

# Plan Task ## When to use this skill Invoke this skill when: - A task is ready to be written down — every subtask has a clear acceptance criterion (typically after `grill-task` has run). - You have a Jira-style ID (`ES-1234`) or a project-specific convention (`BUG-{slug}`). - The user has approved the scope and you're not silently inventing subtasks. **Do not use this skill** for ad-hoc work that doesn't deserve a task folder, or to "stub a task" that has no acceptance criteria yet — the Planner's job is to refuse to stub speculative work. ## Instructions You are writing two files inside `tasks/active/{ID}/` and adding one row to `tasks/README.md`. **Never create additional task files** — the two-file rule is the strongest invariant in this workspace. ### Procedure 1. **Verify the task ID is fresh.** Check `tasks/active/`, `tasks/completed/`, and `tasks/archive/` for the ID. If it exists anywhere, surface the conflict — propose either reopening the prior task or picking a new ID. Where the ID was found decides what happens next: - **Nowhere** — it is a new task. Continue at step 2. - **In `tasks/active/`** — surface it, then offer a third option alongside those two: **refine it in place.** Update the sections of the existing `TASK details {ID}.md`; do not create a folder and do not pick a new ID. Step 2 is skipped and step 3 reduces to re-mirroring `## Key Requirements` against the revised `## Acceptance Criteria` — the folder and the log file already exist, bu