Generate an AsciiDoc task list file. The purpose of this task list is to outline the implementation steps for a project or a specific feature. **File Naming:** * If the task list covers a system-wide implementation (referencing the general PRD and system-wide DESIGN document), name the output file `TASKS.adoc`. * If the task list is for a specific, identifiable task or feature (referencing a task-specific section of the PRD or a task-specific DESIGN document), name the output file `TASKS-[task_identifier].adoc`, replacing `[task_identifier]` with a concise, relevant identifier for that task (e.g., `TASKS-user-authentication.adoc`). **Content and Structure Requirements:** 1. **Source Documents:** * The tasks and their breakdown must be derived directly from the project's **PRD (Product Requirements Document)** and the relevant **DESIGN document(s)**. * Ensure that the generated tasks accurately reflect the requirements and design specifications. 2. **Overall Document Structure (mimic the high-level structure of the provided example `TASKS.adoc`, but generate new task content):** * **Main Title:** Start with a descriptive main title for the checklist, e.g., `= [Project/Feature Name] Implementation Checklist`. * **Table of Contents (TOC):** * Include the following AsciiDoc attributes for TOC generation immediately after the main title: ```asciidoc :toc: :toc-placement!: ``` * After any brief introductory paragraph (if you choose to add one), insert the TOC display command: ```asciidoc toc::[] ``` * **Task Status Legend:** * Include a section titled `== Task Status Legend`. * Define the following status markers within this section: ```asciidoc * ⬜ = Pending task * ✅ = Completed task * ⭕ = Pending Approval * ❌ = Failed task * ❓ = Needs clarification ``` 3. **Task Breakdown and Grouping:** * Divide the overall implementation into logical, high-level sections (e.g., `== Core Module Setup`, `== API Endpoint Implementation`, `== User Interface Development`, `== Testing and QA`). These sections should represent major components, phases, or deliverables as identified in the PRD and DESIGN documents. * Under each high-level section, list specific, actionable subtasks as bullet points. * Each subtask must begin with a status marker, defaulting to `⬜` for pending tasks. Example: ```asciidoc == Logical Group Section (e.g., Backend API) * ⬜ Define data models based on DESIGN-xyz. * ⬜ Implement CRUD operations as per PRD-123. * ⬜ Set up authentication middleware. ``` * Ensure subtasks are sufficiently granular to facilitate clear progress tracking and management. 4. **Syntax:** * The entire output must strictly adhere to AsciiDoc syntax. **Contextual Information (to be provided by you when using this prompt):** * Specify whether this is a system-wise implementation or for a specific task. * Clearly state the `[Project/Feature Name]` and `[task_identifier]` if applicable. * Provide the relevant PRD and DESIGN document(s) or sufficient excerpts/summaries for the AI to derive the tasks.