Refactor task management structure and update documentation

- Changed the directory structure for task specifications to include a dedicated `todo/` folder within `_docs/02_tasks/` for tasks ready for implementation.
- Updated references in various skills and documentation to reflect the new task lifecycle, including changes in the `implementer` and `decompose` skills.
- Enhanced the README and flow documentation to clarify the new task organization and its implications for the implementation process.

These updates improve task management clarity and streamline the implementation workflow.

.cursor/skills/new-task/SKILL.md

@@ -31,13 +31,14 @@ Guide the user through defining new functionality for an existing codebase. Prod
 Fixed paths:
 
 - TASKS_DIR: `_docs/02_tasks/`
+- TASKS_TODO: `_docs/02_tasks/todo/`
 - PLANS_DIR: `_docs/02_task_plans/`
 - DOCUMENT_DIR: `_docs/02_document/`
 - DEPENDENCIES_TABLE: `_docs/02_tasks/_dependencies_table.md`
 
-Create TASKS_DIR and PLANS_DIR if they don't exist.
+Create TASKS_DIR, TASKS_TODO, and PLANS_DIR if they don't exist.
 
-If TASKS_DIR already contains task files, scan them to determine the next numeric prefix for temporary file naming.
+If TASKS_DIR already contains task files (scan `todo/`, `backlog/`, and `done/`), use them to determine the next numeric prefix for temporary file naming.
 
 ## Workflow
 
@@ -195,13 +196,13 @@ Present using the Choose format for each decision that has meaningful alternativ
 **Role**: Technical writer
 **Goal**: Produce the task specification file.
 
-1. Determine the next numeric prefix by scanning TASKS_DIR for existing files
+1. Determine the next numeric prefix by scanning all TASKS_DIR subfolders (`todo/`, `backlog/`, `done/`) for existing files
 2. Write the task file using `.cursor/skills/decompose/templates/task.md`:
    - Fill all fields from the gathered information
    - Set **Complexity** based on the assessment from Step 2
-   - Set **Dependencies** by cross-referencing existing tasks in TASKS_DIR
+   - Set **Dependencies** by cross-referencing existing tasks in TASKS_DIR subfolders
    - Set **Jira** and **Epic** to `pending` (filled in Step 7)
-3. Save as `TASKS_DIR/[##]_[short_name].md`
+3. Save as `TASKS_TODO/[##]_[short_name].md`
 
 **Self-verification**:
 - [ ] Problem section clearly describes the user need
@@ -259,7 +260,7 @@ Ask the user:
 
 After the user chooses **Done**:
 
-1. Update (or create) `TASKS_DIR/_dependencies_table.md` — add all newly created tasks to the dependencies table
+1. Update (or create) `DEPENDENCIES_TABLE` — add all newly created tasks to the dependencies table
 2. Present a summary of all tasks created in this session:
 
 ```