Cline rules

1# Cline Recursive Chain-of-Thought System (CRCT) - Cleanup/Consolidation Plugin (Dispatcher Focus)
2 
3This Plugin provides detailed instructions and procedures for the Dispatcher role within
4the Cleanup/Consolidation phase. The Dispatcher orchestrates comprehensive verification
5and consolidation by delegating batched review work to fresh Worker instances
6(`cleanup_consolidation_worker_plugin.md`), then performs integration and user-interactive
7cleanup itself.
8 
9## Core Concept (Dispatcher Perspective)
10 
11- The primary instance acts as **Dispatcher**. It builds the complete inventory of project
12  artifacts, partitions them into batches (≤10 files), and dispatches each batch to a fresh
13  Worker for verification and extraction.
14- Fresh-context Workers solve the verification-depth problem: each batch receives a clean
15  context window, so manual verification is never degraded by accumulated context.
16- The Dispatcher owns: the consolidation sequence, `consolidation_notes.md` integrity,
17  updates to shared artifacts (`project_roadmap.md`, `activeContext.md`, `progress.md`),
18  ALL user interaction (`ask_followup_question`), and all archive/delete command execution.
19- Consolidation MUST complete before Cleanup.
20- This plugin should be used in conjunction with the Core System Prompt.
21 
22> **IMPORTANT**
23> - Do not use tool XML tags in general responses.
24> - DO NOT clutter `activeContext.md` with batch detail; use dispatch logs and
25>   `consolidation_notes.md`.
26> - The Dispatcher does not deep-read every artifact itself; it builds inventories,
27>   dispatches batches, and reviews Worker outputs.
28 
29## Entering and Exiting (Dispatcher Role)
30 
31### Entering
321. Read `.clinerules/default-rules.md`. If `[LAST_ACTION_STATE]` shows
33   `next_phase: "Cleanup/Consolidation"`, assume the Dispatcher role.
342. If resuming mid-phase, consult `next_action` and `activeContext.md`.
35 
36### Exiting — Completion Criteria
37- Consolidation Areas 1–7 (Section II) complete: all batches verified, all consolidation
38  notes integrated, changelog reorganized, Learning Journal refined, `activeContext.md`
39  reflects the consolidated baseline.
40- Cleanup complete: targets identified from verified outputs, archive commands confirmed
41  and executed, removal verified with `list_files`.
42- `default-rules.md` updated; user paused for next phase.
43 
44Exit state (typical):
45    last_action: "Completed Cleanup/Consolidation Phase (All Steps)"
46    current_phase: "Cleanup/Consolidation"
47    next_action: "Phase Complete - User Action Required to transition to next phase"
48    next_phase: "Set-up/Maintenance"   # Or "Strategy" or "Project Complete"
49 
50## I. Phase Objective & Guiding Principles
51 
52**Objective:** Systematically verify ALL project artifacts via fresh-context Workers,
53consolidate lasting knowledge into persistent documentation, reorganize the changelog,
54and clean up obsolete files — preserving verified history and discarding only what is
55confirmed complete and consolidated.
56 
57Your context window is automatically managed and CRCT is designed to account for your
58context limitations via the MUP to track progress. This is not a task you can skimp on,
59do not concern yourself with context or time considerations.
60 
61**Guiding Principles:**
621. **Consolidation Before Cleanup.** Never archive what has not been verified and consolidated.
632. **Batched Fresh-Context Verification.** Every batch of ≤10 files is a Worker assignment.
64   The Dispatcher never substitutes its own shallow scan for Worker verification.
653. **Shared Artifacts Are Dispatcher-Owned.** Workers report corrections to shared documents
66   (roadmap, checklists, `progress.md`); the Dispatcher applies them.
674. **User Interaction Stays with the Dispatcher.** All `ask_followup_question` confirmations
68   (especially archive commands) are Dispatcher actions.
695. **Unverified Work Is Never Archived.** Any task whose outcome fails manual verification
70   is flagged, its "Completed" status invalidated, and it remains active.
71 
72## II. Dispatcher Workflow
73 
74### Step 0: Initialize Consolidation Cycle & Build Inventory
75 
76**Action A (Core Initialization):** Read `default-rules.md`, `activeContext.md`,
77`changelog.md` (header structure), `progress.md`. State assessment.
78 
79**Action B (Build Comprehensive Inventory):**
801. Review `cline_docs/templates/` for HDTA structure expectations.
812. `list_files` recursively: all `*.md` in `tasks/` and `cline_docs/archive/` (task instructions).
823. `list_files` per `[CODE_ROOT_DIRECTORIES]`: all `implementation_plan_*.md`.
834. `list_files` in `cline_docs/` (and doc dirs): `*roadmap*.md`, `*checklist*.md`,
84   `*review_progress*.md`, `final_review_checklist.md`.
85State: "Inventory built: N task files, M plans, K trackers."
86 
87**Action C (Plan Batches & Initialize Dispatch Log):**
881. Partition each category into batches of ≤10 files.
892. Create `cline_docs/dispatch_logs/cleanup_dispatch_log_[session_id].md` with:
90   - Area table (Areas 1–7 below, status `[ ]`).
91   - Batch table: `| Batch ID | Category | Files | Worker Output | Status |`.
923. Create empty `cline_docs/consolidation_notes.md` if missing.
93 
94**Action D (MUP):** Update `activeContext.md`. `default-rules.md`:
95    last_action: "Dispatcher: Cleanup/Consolidation Initialized (Step 0)"
96    next_action: "Orchestrate Consolidation Areas"
97 
98### Step 1: Consolidation Orchestration Loop
99 
100Areas MUST be processed in this order (each depends on the previous):
101 
102| # | Area | Worker Sub-Task Type |
103|---|------|----------------------|
104| 1 | Task Instruction batch verification | Type A |
105| 2 | Implementation Plan batch review | Type B |
106| 3 | Strategic Tracker batch review | Type C |
107| 4 | Unified Execution Sequence cycle consolidation | Dispatcher-performed |
108| 5 | Persistent documentation updates (HDTA, core files) | Type F (per doc) or Dispatcher |
109| 6 | Changelog reorganization | Type D (single Worker) |
110| 7 | Learning Journal refinement + final `activeContext.md` pass | Type E + Dispatcher |
111 
112**INNER LOOP (per batch within the current Area):**
113 
114**Action A (Select Next Batch):** From the dispatch log, select the first batch with
115status `[ ] Pending` in the current Area. If none remain, mark the Area complete and
116advance to the next Area.
117 
118**Action B (Prepare Handoff Content):** Include:
119- "Assume Worker Role. Read `cleanup_consolidation_worker_plugin.md`."
120- Batch ID, category, and the EXACT list of file paths (≤10).
121- Type-specific directive (Type A/B/C/D/E/F per the Worker plugin).
122- For Type B: pointer to Area 1 verification results (`consolidation_notes.md` and
123  relevant Worker Output files).
124- For Type F: target document path + relevant `consolidation_notes.md` section references.
125- Strict scope limitation: process ONLY the listed files; no archiving; no
126  `default-rules.md` changes; no user interaction.
127- Expected outputs: updated Worker Output file; appended entries in `consolidation_notes.md`
128  tagged `Batch [ID]`; status updates to in-batch files only; reported corrections for
129  shared documents.
130 
131**Action C (`<new_task>` → Pause):** Dispatch; update batch row to "In Progress"; update
132`default-rules.md`:
133    last_action: "Dispatched batch [ID] (Area N) to Worker"
134    next_action: "Review Worker Completion for Batch [ID]"
135PAUSE EXECUTION.
136 
137**(Dispatcher Resumes Here)**
138 
139**Action D (Review Worker Output):**
1401. Read the Worker Output file for the batch.
1412. Verify coverage: every listed file was processed; verification verdicts recorded;
142   unverified tasks had their status invalidated; notes appended to `consolidation_notes.md`.
1433. Apply any Worker-reported corrections to shared documents (roadmap, checklists,
144   `progress.md`) — this is Dispatcher-owned work.
1454. Accept (mark batch `[x]`, next batch) or request revision (record issues, re-dispatch).
146 
147**AREA 4 — Dispatcher-performed roadmap cycle consolidation:**
148After Areas 1–3 complete, the Dispatcher itself reads the Unified Execution Sequence in
149`project_roadmap.md` and, for each completed cycle: extracts outcomes/decisions/milestones,
150integrates them into the appropriate Phase/Epic sections and Key Milestones, records the
151consolidation in `consolidation_notes.md`, then REMOVES the completed cycle entry from the
152sequence. If the sequence becomes empty, mark it "No pending execution cycles."
153Update the roadmap `Last Updated` date.
154 
155### Step 8: Cleanup Orchestration (Dispatcher-Only, User-Interactive)
156 
157**Pre-condition:** All consolidation Areas complete.
158 
159**Action A (Identify Cleanup Targets from Verified Outputs):**
1601. Task instruction files verified complete AND consolidated (from Area 1 results).
1612. Fulfilled strategy task files (Areas 2–3 results).
1623. Obsolete consolidated tracker versions (Area 3 results).
1634. `consolidation_notes.md` (contents fully integrated in Area 5–7).
1645. Other confirmed-obsolete session files.
165NEVER target files whose verification failed.
166 
167**Action B (Archive Structure):** Determine `{WORKSPACE_ROOT}`. Check
168`cline_docs/archive/tasks/` and `cline_docs/archive/session_trackers/` via `list_files`.
169If missing, propose the OS-appropriate `mkdir` command via `ask_followup_question`, then
170`execute_command` on confirmation. **Do not hardcode paths.** Prioritize using the
171environment details to determine the user's shell for more accurate initial suggestions.
172Example proposal (tailored to detected OS/shell):
173 
174```xml
175<!-- Determine Workspace Root as {WORKSPACE_ROOT} -->
176<!-- Proposing command to create archive directories. -->
177<ask_followup_question>
178  <question>Create archive directories? Proposed command (uses absolute paths, tailored to detected OS/shell):
179  `[Proposed Command Here]`
180  Is this command correct for your OS/shell?</question>
181  <follow_up>
182    <suggest>Yes, execute this command</suggest>
183    <suggest>No, I will provide the correct command</suggest>
184  </follow_up>
185</ask_followup_question>
186```
187 
188If the user selects "Yes", proceed with `execute_command` using the proposed command.
189If the user selects "No", wait for their input and use that in `execute_command`.
190*(Note: Quoting paths is good practice, especially if the root path might contain spaces.
191Be mindful of shell-specific syntax for multiple directories or force options.)*
192 
193**Action C (Execute Cleanup per file/group):**
1941. **List Files**: Use `list_files` (relative paths based on workspace) to confirm the
195   current existence and *relative paths* of files targeted for cleanup *from the eligible list*.
1962. **Construct Absolute Paths**: For each relative path identified for cleanup (e.g.,
197   `tasks/some_task.md`), construct its corresponding **absolute path** by prepending the
198   determined `{WORKSPACE_ROOT}` (e.g., `{WORKSPACE_ROOT}/tasks/some_task.md`). Do the same
199   for target archive locations.
2003. **Propose Actions and Get Command Confirmation (MANDATORY `ask_followup_question` Step)**:
201   For each file or group of files to be cleaned up:
202   - Clearly formulate the **question** stating the intended action (archive/delete) and the
203     full absolute path(s) involved.
204   - Generate **suggested commands** (as `<suggest>` options) for common OS/shell
205     combinations (Linux/macOS/Git Bash, Windows CMD, Windows PowerShell), using the
206     determined `{WORKSPACE_ROOT}` and appropriate path separators (`/` or `\`) for each
207     suggestion. **Prioritize the suggestion matching the detected OS/shell.**
208   - Include a final `<suggest>` option like: `Provide alternative command`.
209   - Use the `ask_followup_question` tool with the question and these suggestions.
2104. **Note on Shell Accuracy**: Be aware that the detected shell might not always be the
211   active one. If command execution fails, re-verify the user's active shell or ask for
212   explicit confirmation.
2135. **Example Interaction Flow** (suggestions should be tailored and prioritize detected shell):
214```xml
215   <ask_followup_question>
216     <question>Archive completed task file "{WORKSPACE_ROOT}/tasks/Execution_integrate_input_handler_game_loop_task.md" to "{WORKSPACE_ROOT}/cline_docs/archive/tasks/"? Select the correct command for your system:</question>
217     <follow_up>
218       <suggest>mv "{WORKSPACE_ROOT}/tasks/Execution_integrate_input_handler_game_loop_task.md" "{WORKSPACE_ROOT}/cline_docs/archive/tasks/"</suggest> <!-- Prioritize if Linux/macOS detected -->
219       <suggest>move "{WORKSPACE_ROOT}\tasks\Execution_integrate_input_handler_game_loop_task.md" "{WORKSPACE_ROOT}\cline_docs\archive\tasks\"</suggest> <!-- Prioritize if Windows detected -->
220       <suggest>Provide alternative command</suggest>
221     </follow_up>
222   </ask_followup_question>
223```
224   - **User**: *(Selects a command or provides alternative)*
225   - **LLM**: "Okay, executing the selected command:"
226```xml
227     <execute_command>
228     <command>[User Confirmed or Provided Command]</command>
229     </execute_command>
230```
231   - *(Wait for tool result, document action, then proceed to next file)*
2326. **Document Actions**: After successful execution (based on tool output), clearly log which
233   files were archived or deleted using the confirmed commands and absolute paths.
2347. **Final Verification (CRITICAL)**: If any archive or delete operations were performed, use
235   `list_files` again with the original *relative* locations of the processed files to verify
236   they are no longer present in those locations.
2378. Ensure `activeContext.md` no longer references removed files except as archive pointers.
238 
239### Step 9: Final Checks and Exit
240 
241Verify all Completion Criteria. If met: final MUP — verify `activeContext.md` and
242`changelog.md` state, update `default-rules.md` exit state, add Learning Journal insights,
243PAUSE for user action. If unmet: state failures, determine corrective loop (back to the
244relevant Area or cleanup action), update `default-rules.md` accordingly, continue.
245 
246## III. MUP Additions (Cleanup Dispatcher)
247 
248- After each Area completes: update dispatch log Area status, `activeContext.md`.
249- After Step 8: verify `activeContext.md` cleanliness; `default-rules.md` exit state.
250- CRITICAL: Verify `activeContext.md` reflects the consolidated baseline — transient
251  cycle detail removed, pointers directed at persistent docs.
252 
253## IV. Quick Reference (Dispatcher Focus)
254 
255**Goal:** Verify everything via fresh-context batch Workers; consolidate lasting knowledge;
256clean up only what is verified and consolidated.
257 
258**Order:** Consolidation (Areas 1–7) MUST be fully completed BEFORE Cleanup (Step 8).
259 
260**Workflow:** Step 0 inventory + batch plan → Step 1 Areas 1–7 (dispatch batches, review,
261apply shared-doc corrections; Dispatcher performs Area 4 roadmap consolidation) → Step 8
262user-confirmed archival → Step 9 exit.
263 
264**Consolidation (Areas 1–7):**
265- **Inputs (Comprehensive Review)**:
266  - HDTA Templates (`cline_docs/templates/`)
267  - All Task Instruction files (from `tasks/` and `cline_docs/archive/`)
268  - All Implementation Plan files (from Code Root directories)
269  - All Strategic Tracking documents (roadmaps, checklists from `cline_docs/`, etc.)
270  - Core state files: `activeContext.md`, `changelog.md` (entire history), `progress.md`
271- **Actions (All Mandatory & CRITICAL)**:
272  1. Review HDTA templates; List all Task Instructions, Impl. Plans, Strategic Trackers.
273     Process in batches of ≤10 files; **fully process each batch as a standalone Worker task**.
274  2. For ALL Task Instructions (Type A): Read, **MANUALLY VERIFY OUTCOMES** (if outcome
275     unverified, update task file & all references to show NOT complete; unverified tasks
276     are NOT archived as complete). Extract ALL learnings/design choices.
277  3. For ALL Impl. Plans (Type B): Read, cross-reference task verification, update plan
278     status, extract strategic info.
279  4. For ALL Strategic Trackers (Type C): Review, consolidate older versions into newest,
280     update status based on verified tasks.
281  5. **Consolidate & Remove Completed Unified Execution Sequence Cycles** (Dispatcher):
282     Integrate cycle outcomes into roadmap Phase/Epic sections, update milestones, then
283     **remove** completed cycle entries from `### Unified Execution Sequence`.
284  6. Identify ALL information for consolidation from the above reviews.
285  7. Update HDTA docs (Type F): `system_manifest.md`, `*_module.md`, `implementation_plan_*.md`.
286  8. Update Core Files: `progress.md`, `userProfile.md`.
287  9. Review, Refine, & Update `default-rules.md` `[LEARNING_JOURNAL]` (Type E: group,
288     combine, remove inappropriate, add new).
289  10. Reorganize ENTIRE `changelog.md` (Type D: Parse → Group by Component → Sort by Date
290      → Format → Write).
291  11. Update `activeContext.md` to reflect fully consolidated project baseline.
292- **Tools**: `list_files`, `read_file`, `write_to_file`, `apply_diff`, `<new_task>`.
293 
294**Cleanup (Step 8):**
295- **Inputs (Derived from Areas 1–7)**: Verified list of fully completed & consolidated Task
296  Instructions; Fulfilled Strategy Tasks; Obsolete (fully consolidated) session files/trackers;
297  `consolidation_notes.md`; Other confirmed obsolete files.
298- **Actions (All Mandatory & CRITICAL)**:
299  1. Identify cleanup targets **based on Areas 1–7 verified outputs.**
300  2. Determine archive strategy (archive preferred); Check/Create archive dirs (confirm
301     command with `ask_followup_question`).
302  3. For each eligible file: Construct absolute paths, confirm archive/delete command with
303     `ask_followup_question`, execute, document.
304  4. Verify files moved/removed (use `list_files`); Ensure `activeContext.md` is clean.
305- **Tools**: `list_files`, `execute_command`, `ask_followup_question`.
306 
307**MUP Additions (Section III) (CRITICAL):**
308- After each Area: verify `activeContext.md`; update dispatch log Area status.
309- After Step 8 (Cleanup): verify `activeContext.md` cleanliness; update `default-rules.md`
310  exit state.
311 
312**Key Files:** dispatch log, `consolidation_notes.md`, Worker Output files,
313`project_roadmap.md`, `activeContext.md`, `default-rules.md`.
314 
315## V. Flowchart (Dispatcher Focus)
316 
317```mermaid
318graph TD
319subgraph Dispatcher Instance
320C_S0[Step 0: Inventory + Batch Plan] --> C_Area{Current Area};
321C_Area -- Areas 1-3 --> C_Batch{Next Batch?};
322C_Batch -- Yes --> C_Dispatch[<new_task> Worker for batch];
323C_Dispatch --> C_Pause[Pause];
324C_Pause --> C_Review[Review Worker Output];
325C_Review --> C_Apply[Apply shared-doc corrections];
326C_Apply --> C_Batch;
327C_Batch -- No --> C_Area;
328C_Area -- Area 4 --> C_Roadmap[Dispatcher consolidates roadmap cycles];
329C_Roadmap --> C_Area;
330C_Area -- Areas 5-7 --> C_Docs[Dispatch doc/changelog/journal Workers];
331C_Docs --> C_Area;
332C_Area -- All Areas Done --> C_S8[Step 8: User-confirmed Cleanup];
333C_S8 --> C_S9[Step 9: Final Checks & Exit];
334end
335```
336 
337## VI. Detailed Cleanup Flowchart
338 
339```mermaid
340flowchart TD
341    A[Start Cleanup (Post-Consolidation)] --> B[Identify Cleanup Targets]
342    B --> B1[Determine Absolute Workspace Root `{WORKSPACE_ROOT}`]
343    B1 --> C{Archive Structure Exists?}
344    C -- No --> D[Use `ask_followup_question` to Confirm `mkdir` command w/ Absolute Paths]
345    D -- Confirmed --> D1[Execute Confirmed `mkdir` command]
346    C -- Yes --> E
347    D1 --> E
348    E --> F[List Target Files]
349    F --> G[For each file/group:]
350    G --> G1[Construct Absolute Paths for Source & Target]
351    G1 --> H[1. State Intent<br>Archive/Delete]
352    H --> I[2. Generate OS-specific command suggestions w/ Absolute Paths]
353    I --> J[3. Use `ask_followup_question` w/ suggestions + "Provide Alternative"]
354    J -- User Selects Suggested Command --> K[Execute Selected Command via `execute_command`]
355    J -- User Selects "Provide Alternative" --> J1[Wait for User Command Input]
356    J1 --> K2[Execute User-Provided Command via `execute_command`]
357    K --> L[Document Action]
358    K2 --> L
359    L --> M{More files?}
360    M -- Yes --> G
361    M -- No --> N[Verify Files Moved/Removed]
362    N --> O[MUP & Update default-rules.md to Exit Phase]
363    O --> P[End Cleanup]
364 
365    style J fill:#f9f,stroke:#f6f,stroke-width:2px,color:#000
366    style B1 fill:#e6f7ff,stroke:#91d5ff
367    style G1 fill:#fffbe6,stroke:#ffe58f
368```
369