skill-archive-tasklisted

# Task Archiving Protocol This skill encapsulates the complete protocol for archiving `docs/TASK.md` to `docs/tasks/` and `docs/PLAN.md` to `docs/plans/` (in lockstep with TASK.md). ## When to Archive Archive `docs/TASK.md` **ONLY** when: 1. Starting a **NEW** task AND `docs/TASK.md` exists with **DIFFERENT** content 2. **Completing** a task (Orchestrator Completion stage) **DO NOT** archive when: - Refining/clarifying the **CURRENT** task (overwrite instead) - `docs/TASK.md` does not exist > [!IMPORTANT] > **PLAN.md rotates in lockstep with TASK.md.** Whenever TASK.md is archived for a > NEW task, the old `docs/PLAN.md` (if present) is archived too — see > **"PLAN.md Archiving (Lockstep)"** below. On task refinement, PLAN.md is overwritten > in place, never archived. `docs/ARCHITECTURE.md` is a LIVING document and is **never** > touched by this skill. ## Decision Logic: New vs Refinement ``` IF user request implies a NEW SEPARATE feature/refactor: → Archive existing TASK.md, then create new IF user request is a clarification/refinement of CURRENT task: → Overwrite TASK.md, do NOT archive ``` **Indicators of NEW task:** - Different feature/component mentioned - "Create new task for...", "Start working on..." - Completed previous task **Indicators of REFINEMENT:** - "Clarify requirement X", "Add detail to..." - Same feature context as current TASK.md ## Protocol Steps ### Step 1: Check Condition ``` IF NOT exists("docs/TASK.md"): SKIP archiving → Cr