# io8 Business Analyst Agent - Customized for This Project

## Project-Specific Instructions

```json
{
  "analysis": "```markdown\n## Project Overview - Notes Application (Generated: 2025-10-06 {current_timestamp})\nThis project extends an existing Angular Clarity Boilerplate base project to develop a fully functional, working notes application. The application will enable users to manage their personal notes, including creation, viewing, editing, and deletion, with secure user authentication.\n\n## Business Analysis - Notes Application\nThe primary business objective is to provide a user-friendly and reliable digital note-taking solution. The notes app aims to enhance user productivity by offering a centralized and secure platform for storing personal information, ideas, and reminders. It addresses the common need for organized information management and provides a foundation for future feature expansion (e.g., advanced search, collaboration). The secure user management ensures data privacy and integrity.\n\n## User Requirements - Notes Application\n(Extracted from .io8codermaster_breakdown.md addendum - Section 5. Detailed Functional Requirements)\n\n### Note Management (CRUD):\n*   Users must be able to create new notes with a title and rich-text content.\n*   Users must be able to view a list of all their notes, with options for sorting (e.g., by date created, last modified).\n*   Users must be able to view individual notes in detail.\n*   Users must be able to edit existing notes (title, content).\n*   Users must be able to delete notes.\n\n### User Management & Authentication:\n*   Users must be able to register (sign-up) with an email and password.\n*   Users must be able to log in (sign-in) using their registered credentials.\n*   The system must ensure secure access to user-specific notes, meaning users can only view, edit, or delete their own notes.\n*   A basic password reset functionality must be available.\n\n### Search & Organization (MVP Optional, Phase 3 focus):\n*   Users should ideally be able to search notes by title or content keywords.\n*   Users should ideally be able to apply basic categorization or tagging to their notes.\n\n## Functional Requirements - Notes Application\n(Detailed breakdown from user requirements)\n\n*   **Note Creation:** Allow users to input a title and rich-text content to create a new note.\n*   **Note Listing:** Display all notes belonging to the authenticated user in a structured list, with options to sort by creation date or last modified date.\n*   **Note Detail Viewing:** Present the full title and rich-text content of a selected note.\n*   **Note Editing:** Provide an interface for users to modify the title and rich-text content of an existing note.\n*   **Note Deletion:** Implement a mechanism for users to permanently remove a note after confirmation.\n*   **User Registration:** Enable new users to create an account by providing an email and password.\n*   **User Login:** Authenticate existing users based on their email and password.\n*   **Secure Note Ownership:** Enforce that only the creator of a note can access, modify, or delete it.\n*   **Password Reset:** Offer a basic process for users to reset forgotten passwords.\n*   **Note Search (Optional):** Implement a search bar to filter notes by keywords in their title or content.\n*   **Note Categorization/Tagging (Optional):** Allow users to assign predefined categories or custom tags to notes for better organization.\n\n## Non-Functional Requirements - Notes Application\n\n*   **Performance:**\n    *   Login and registration processes should complete within 3 seconds under normal load.\n    *   Note CRUD operations (create, retrieve, update, delete) should respond within 2 seconds.\n    *   The application should remain responsive when displaying up to 100 notes in the list view.\n*   **Security:**\n    *   User passwords must be securely hashed and stored (e.g., using bcrypt).\n    *   User authentication must utilize industry-standard practices (e.g., JWT for session management).\n    *   All communications between frontend and backend must be secured using HTTPS.\n    *   Authorization checks must be performed on the backend for all note operations to ensure users only interact with their own data.\n*   **Usability:**\n    *   The user interface should be intuitive and easy to navigate, leveraging the Clarity Design System for consistency.\n    *   The application must be fully responsive, adapting to various screen sizes (desktop, tablet, mobile).\n    *   Error messages should be clear, concise, and helpful.\n*   **Scalability:**\n    *   The backend API and database should be designed to support an increasing number of users and notes without significant degradation in performance.\n    *   The containerized architecture (Docker, Docker Compose) should facilitate horizontal scaling in production environments.\n*   **Maintainability:**\n    *   The codebase should follow established best practices for Angular, the chosen backend framework, and TypeScript.\n    *   Code should be well-documented, and tests should be comprehensive to ensure future modifications are manageable.\n*   **Reliability:**\n    *   User data, especially notes, must be persisted reliably in the database.\n    *   The system should handle unexpected errors gracefully and prevent data loss.\n\n## User Stories - Notes Application\n\n*   **As a new user**, I want to register for an account **so that** I can securely store my notes.\n    *   **Acceptance Criteria:**\n        *   Given I am on the registration page,\n        *   When I enter a valid email and password, and confirm the password,\n        *   Then my account should be created, and I should be redirected to the login page or a notes dashboard.\n*   **As a registered user**, I want to log in to my account **so that** I can access my personal notes.\n    *   **Acceptance Criteria:**\n        *   Given I am on the login page,\n        *   When I enter my registered email and password,\n        *   Then I should be authenticated and gain access to my notes.\n*   **As a logged-in user**, I want to create a new note with a title and rich-text content **so that** I can record my thoughts or information.\n    *   **Acceptance Criteria:**\n        *   Given I am on the notes dashboard and logged in,\n        *   When I click 'Create New Note' and fill in the title and content fields,\n        *   Then a new note should be saved and appear in my list of notes.\n*   **As a logged-in user**, I want to view a list of all my notes **so that** I can quickly browse and select one.\n    *   **Acceptance Criteria:**\n        *   Given I am logged in,\n        *   When I navigate to the notes list,\n        *   Then I should see a list of my notes, each showing at least its title and last modified date.\n*   **As a logged-in user**, I want to view the full content of a specific note **so that** I can read its details.\n    *   **Acceptance Criteria:**\n        *   Given I am viewing the list of notes,\n        *   When I select a note,\n        *   Then I should be taken to a detail view displaying the note's full title and rich-text content.\n*   **As a logged-in user**, I want to edit an existing note's title and content **so that** I can update my information.\n    *   **Acceptance Criteria:**\n        *   Given I am viewing a note's details,\n        *   When I click 'Edit' and modify the title or content,\n        *   Then the changes should be saved, and the updated note should be reflected in the detail view and list.\n*   **As a logged-in user**, I want to delete a note **so that** I can remove outdated or unwanted information.\n    *   **Acceptance Criteria:**\n        *   Given I am viewing a note's details or the notes list,\n        *   When I choose to delete a note and confirm my action,\n        *   Then the note should be permanently removed from my notes.\n*   **As a logged-in user**, I want to reset my password **so that** I can regain access to my account if I forget it.\n    *   **Acceptance Criteria:**\n        *   Given I am on the login page and click 'Forgot Password',\n        *   When I provide my registered email,\n        *   Then I should receive instructions (e.g., a link) to reset my password.\n\n## Business Rules - Notes Application\n\n*   All notes must belong to an authenticated user.\n*   A note must have a title (cannot be empty).\n*   The content of a note can be empty.\n*   Only the creator of a note can view, edit, or delete that note.\n*   User email addresses must be unique for registration.\n*   Passwords must meet minimum complexity requirements (e.g., minimum length, mix of character types - to be defined).\n*   Deleted notes are permanently removed and cannot be recovered.\n\n```\n",
  "requirements": "```markdown\n## Functional Requirements - Notes Application\n(Generated: 2025-10-06 {current_timestamp})\n\n### FR-001: User Registration\n- **Description:** The system shall allow new users to register for an account by providing a unique email address and a secure password.\n- **Acceptance Criteria:**\n    - Given I am on the registration page,\n    - When I submit valid and unique credentials (email, password, confirm password),\n    - Then a new user account shall be created, and I shall be able to log in with these credentials.\n    - When I submit an email that is already registered,\n    - Then the system shall display an error message indicating the email is taken.\n    - When passwords do not match,\n    - Then the system shall display an error message.\n- **Priority:** High\n\n### FR-002: User Login\n- **Description:** The system shall allow registered users to log in to their accounts using their email and password.\n- **Acceptance Criteria:**\n    - Given I am on the login page,\n    - When I enter my registered email and correct password,\n    - Then I shall be authenticated and granted access to my notes dashboard.\n    - When I enter incorrect credentials,\n    - Then the system shall display an error message (e.g., \"Invalid credentials\").\n- **Priority:** High\n\n### FR-003: Password Reset\n- **Description:** The system shall provide a basic mechanism for users to reset their forgotten passwords.\n- **Acceptance Criteria:**\n    - Given I am on the login page and click \"Forgot Password\",\n    - When I enter my registered email address,\n    - Then the system shall provide instructions (e.g., via email, or a direct form for simple implementation) to reset my password.\n- **Priority:** Medium\n\n### FR-004: Create New Note\n- **Description:** The system shall allow an authenticated user to create a new note with a title and rich-text content.\n- **Acceptance Criteria:**\n    - Given I am logged in,\n    - When I initiate creating a new note and provide a non-empty title and optional rich-text content,\n    - Then the note shall be saved and associated with my user account.\n    - The new note shall appear in my list of notes.\n    - When I attempt to save a note with an empty title,\n    - Then the system shall display an error message and prevent saving.\n- **Priority:** High\n\n### FR-005: View All Notes\n- **Description:** The system shall display a list of all notes created by the authenticated user.\n- **Acceptance Criteria:**\n    - Given I am logged in and navigate to the notes list,\n    - Then I shall see a paginated/scrollable list of my notes.\n    - Each item in the list shall display at least the note's title and its last modified date.\n    - The list shall offer options to sort notes by creation date (ascending/descending) and last modified date (ascending/descending).\n- **Priority:** High\n\n### FR-006: View Individual Note\n- **Description:** The system shall allow an authenticated user to view the full details of a specific note.\n- **Acceptance Criteria:**\n    - Given I am viewing the list of notes and select a specific note,\n    - Then I shall be navigated to a detailed view displaying the note's full title and rich-text content.\n    - This view shall also include options to edit or delete the note.\n- **Priority:** High\n\n### FR-007: Edit Existing Note\n- **Description:** The system shall allow an authenticated user to modify the title and rich-text content of their existing notes.\n- **Acceptance Criteria:**\n    - Given I am viewing a specific note's details,\n    - When I click an \"Edit\" option and modify the title (non-empty) or content fields,\n    - Then the updated note shall be saved and reflected in the detail view and the notes list.\n    - When I attempt to save an edited note with an empty title,\n    - Then the system shall display an error message and prevent saving.\n- **Priority:** High\n\n### FR-008: Delete Note\n- **Description:** The system shall allow an authenticated user to permanently delete their existing notes.\n- **Acceptance Criteria:**\n    - Given I am viewing a specific note's details or the notes list,\n    - When I select a \"Delete\" option,\n    - Then a confirmation prompt shall appear.\n    - When I confirm the deletion,\n    - Then the note shall be permanently removed from the system and no longer appear in my notes list.\n- **Priority:** High\n\n### FR-009: Secure Note Ownership\n- **Description:** The system shall ensure that users can only access, modify, or delete notes that they have created.\n- **Acceptance Criteria:**\n    - Given I am logged in and attempt to access a note not associated with my user ID,\n    - Then the system shall deny access and display an appropriate authorization error.\n- **Priority:** High\n\n### FR-010: Search Notes (Optional MVP)\n- **Description:** The system shall allow an authenticated user to search their notes by keywords present in the title or content.\n- **Acceptance Criteria:**\n    - Given I am viewing my notes list,\n    - When I enter a search term into a search bar,\n    - Then the list of notes shall dynamically filter to show only notes where the title or content matches the search term.\n- **Priority:** Medium\n\n### FR-011: Categorization/Tagging (Optional MVP)\n- **Description:** The system shall allow an authenticated user to assign categories or tags to their notes for better organization.\n- **Acceptance Criteria:**\n    - Given I am creating or editing a note,\n    - When I select or enter tags/categories for the note,\n    - Then these tags/categories shall be saved with the note and visible in the note's detail view.\n    - Users should be able to filter notes by selected tags/categories.\n- **Priority:** Low\n\n## Non-Functional Requirements - Notes Application\n\n### NFR-001: Performance\n- **Description:** The application must provide a responsive user experience with minimal delays for core operations.\n- **Acceptance Criteria:**\n    - Login, registration, and all note CRUD operations (create, retrieve, update, delete) shall complete within 2 seconds under typical load (e.g., 50 concurrent users).\n    - The notes list view shall load and render within 3 seconds for a user with up to 200 notes.\n- **Priority:** High\n\n### NFR-002: Security\n- **Description:** The application must protect user data and ensure secure access to personal notes.\n- **Acceptance Criteria:**\n    - All user passwords shall be stored as strong, one-way hashes (e.g., using bcrypt or similar) in the database.\n    - User authentication shall be implemented using JSON Web Tokens (JWTs) or a comparable secure token-based mechanism.\n    - All communication between the frontend and backend shall be encrypted using HTTPS/SSL.\n    - The backend API shall implement robust input validation to prevent common vulnerabilities (e.g., SQL injection, XSS).\n    - User sessions shall be securely managed with appropriate expiration and renewal policies.\n- **Priority:** Critical\n\n### NFR-003: Usability\n- **Description:** The application must be intuitive, easy to learn, and consistently styled.\n- **Acceptance Criteria:**\n    - The user interface shall adhere to the design principles and components of the Clarity Design System for a consistent look and feel.\n    - Navigation paths for primary features (e.g., viewing notes, creating a new note) shall be clear and require no more than three clicks from the main dashboard.\n    - The application shall be fully responsive and provide an optimal viewing experience across desktop, tablet, and mobile devices.\n    - All error messages and feedback shall be clear, actionable, and user-friendly.\n- **Priority:** High\n\n### NFR-004: Scalability\n- **Description:** The application's architecture must support an increasing number of users and notes without significant performance degradation.\n- **Acceptance Criteria:**\n    - The backend services and database should be capable of handling at least 50 concurrent authenticated users performing note operations without service interruption or significant slowdowns.\n    - The Dockerized components (frontend, backend, database) shall be configured for easy horizontal scaling in a production environment.\n- **Priority:** Medium\n\n### NFR-005: Reliability\n- **Description:** The application must ensure consistent availability and reliable data persistence.\n- **Acceptance Criteria:**\n    - The application shall have an uptime target of 99.9% in a production environment.\n    - All note and user data shall be reliably persisted in the PostgreSQL database, with mechanisms for preventing data corruption or loss.\n    - In the event of an unexpected backend error, the system shall provide graceful error handling and prevent data inconsistencies.\n- **Priority:** High\n\n## Data Requirements - Notes Application\n\n### Entities and Attributes:\n\n*   **User**\n    *   `id` (UUID, Primary Key, Auto-generated)\n    *   `email` (VARCHAR, Unique, Not Null)\n    *   `password_hash` (VARCHAR, Not Null - stores securely hashed password)\n    *   `created_at` (TIMESTAMP, Not Null, Default: current timestamp)\n    *   `updated_at` (TIMESTAMP, Not Null, Default: current timestamp, On Update: current timestamp)\n\n*   **Note**\n    *   `id` (UUID, Primary Key, Auto-generated)\n    *   `user_id` (UUID, Foreign Key referencing `User.id`, Not Null)\n    *   `title` (VARCHAR, Not Null, Max Length: 255)\n    *   `content` (TEXT, Nullable - for rich-text content)\n    *   `created_at` (TIMESTAMP, Not Null, Default: current timestamp)\n    *   `updated_at` (TIMESTAMP, Not Null, Default: current timestamp, On Update: current timestamp)\n\n### Relationships:\n*   One-to-Many: One `User` can have many `Note`s. Each `Note` belongs to exactly one `User`.\n    *   `User.id` (PK) -> `Note.user_id` (FK)\n\n### Data Storage:\n*   PostgreSQL database, managed via Docker.\n*   Migrations will be used to manage schema changes.\n\n## Interface Requirements - Notes Application\n\n### User Interface (UI) Components:\n*   **Login Page:**\n    *   Email input field\n    *   Password input field\n    *   Login button\n    *   Link to Registration page\n    *   Link to Password Reset functionality\n*   **Registration Page:**\n    *   Email input field\n    *   Password input field\n    *   Confirm Password input field\n    *   Register button\n    *   Link to Login page\n*   **Password Reset Page:**\n    *   Email input field (for requesting reset)\n    *   Password Reset Form (for entering new password after verification)\n*   **Notes Dashboard/List View:**\n    *   Header (incorporating branding, user name/avatar, logout option)\n    *   Sidebar (potentially for navigation, filters, tags)\n    *   \"Create New Note\" button/action\n    *   Search bar (for FR-010)\n    *   Sort options (by date created, last modified)\n    *   List/Grid display of notes (each displaying title, last modified date, and possibly a short snippet of content)\n    *   Pagination or infinite scroll for large numbers of notes.\n*   **Note Detail View:**\n    *   Display full note title and rich-text content.\n    *   \"Edit Note\" button/action\n    *   \"Delete Note\" button/action\n    *   Back to notes list navigation.\n*   **Note Create/Edit Form:**\n    *   Title input field (single line)\n    *   Rich-text editor for content (multi-line, basic formatting options)\n    *   \"Save\" button\n    *   \"Cancel\" button\n    *   Tag/Category input (for FR-011)\n\n### API Requirements:\n*   **Base URL:** `/api/v1` (to be defined by io8architect)\n*   **Authentication:** JWT (JSON Web Tokens) for authenticating users for protected routes.\n*   **User Endpoints:**\n    *   `POST /api/v1/register`: User registration.\n    *   `POST /api/v1/login`: User authentication, returns JWT.\n    *   `POST /api/v1/forgot-password`: Initiate password reset.\n    *   `POST /api/v1/reset-password`: Complete password reset.\n*   **Note Endpoints (Authenticated):**\n    *   `POST /api/v1/notes`: Create a new note.\n    *   `GET /api/v1/notes`: Retrieve all notes for the authenticated user (with optional query params for sorting, searching).\n    *   `GET /api/v1/notes/{id}`: Retrieve a specific note by ID.\n    *   `PUT /api/v1/notes/{id}`: Update an existing note by ID.\n    *   `DELETE /api/v1/notes/{id}`: Delete a note by ID.\n\n```\n"
}
```
---
```markdown
.sureai/.io8analyst_agent_develop_a_working_develop_a_working_20251006_065420.md
# io8Analyst Agent Prompt: Develop a Working Notes App

**Project Title:** Working Notes Application (Building upon Angular Clarity Boilerplate)
**User Prompt:** develop a working notes app

## 1. Analysis Methodology Specific to this Project

For the "Develop a Working Notes App" project, the analysis methodology will be iterative and incremental, building directly upon the provided `io8codermaster_breakdown.md` and `io8codermaster_plan.md` addendums.

1.  **Contextual Integration Analysis:** Understand how the new "Notes App" functionality will integrate with the existing "Angular Clarity Boilerplate" base project. This involves identifying which parts of the boilerplate will be extended (e.g., frontend structure, Clarity components) and which parts will be newly developed (e.g., backend, database, specific notes UI).
2.  **Detailed Requirements Elicitation:** Extract and refine the explicit and implicit requirements from the `io8codermaster_breakdown.md` addendum (Section 5: Detailed Functional Requirements for Notes App).
3.  **Prioritization:** Categorize requirements into MVP (Minimum Viable Product) and future enhancements, as indicated in the breakdown (e.g., Search & Organization as optional/Phase 3 focus).
4.  **Decomposition:** Break down high-level user requirements into granular Functional Requirements (FRs), Non-Functional Requirements (NFRs), User Stories, and Business Rules.
5.  **Traceability Mapping:** Ensure all defined requirements are directly traceable back to the user's prompt and the `io8codermaster_breakdown` addendum.

## 2. Requirements Analysis Approach for this User Request

The requirements analysis for the notes app will follow a systematic approach:

1.  **Functional Requirements (FRs):**
    *   **Note Management (CRUD):** Define detailed steps and criteria for creating, viewing (list & detail), editing, and deleting notes. This includes specifying fields (title, content), rich-text capabilities, and user interactions.
    *   **User Management & Authentication:** Detail the flow and security aspects for user registration, login, secure access control (user-specific notes), and password reset.
    *   **Search & Organization:** Outline requirements for searching notes by keywords and basic categorization/tagging, noting their optional MVP status.
2.  **Non-Functional Requirements (NFRs):**
    *   **Performance:** Define acceptable response times for key operations (login, note CRUD, list loading).
    *   **Security:** Specify requirements for user authentication (JWT), password storage (hashing), authorization (user ownership), and data protection (HTTPS).
    *   **Usability:** Ensure the user interface is intuitive, leverages Clarity Design System effectively, and is responsive across devices.
    *   **Scalability:** Consider the ability to handle an increasing number of users and notes, leveraging the Dockerized architecture.
    *   **Reliability & Maintainability:** Address data persistence, error handling, and code quality.
3.  **Data Requirements:** Based on functional needs, define the data model for `User` and `Note` entities, including attributes, data types, relationships (e.g., one-to-many between User and Note), and key constraints.
4.  **Interface Requirements:** Sketch out high-level UI components needed for each functional area (e.g., login form, notes list, note editor) and define API endpoints for frontend-backend communication, as per the `io8codermaster_breakdown` addendum's technical stack.

## 3. Business Analysis Framework

The business analysis will primarily utilize a **Functional Decomposition** and **Feature-driven Analysis** framework, supported by elements of a **Value Proposition Canvas** implicit in the notes app's core purpose.

*   **Functional Decomposition:** Break down the core "Notes App" into primary functions (User Management, Note Management) and then into sub-functions (e.g., within Note Management: Create Note, View Note List, View Note Detail, Edit Note, Delete Note).
*   **Feature-Driven Analysis:** Each function identified will be treated as a distinct feature, for which detailed requirements will be gathered, user stories written, and acceptance criteria defined. This ensures comprehensive coverage of all intended capabilities.
*   **Value Proposition (Implicit):** While not explicitly creating a full canvas, the analysis will ensure the defined features deliver clear value to the end-user (e.g., efficient organization, secure personal data, ease of use).

## 4. User Story Development Strategy

User stories will be developed using the standard "As a [User Role], I want to [Action] so that [Benefit]" template, complemented by clear, testable acceptance criteria using a Gherkin-like syntax where appropriate.

*   **Identify User Roles:** The primary user role is "registered user" or "logged-in user," with "new user" for registration.
*   **Define Actions:** Map directly to the functional requirements (e.g., "create a new note," "log in to my account").
*   **State Benefits:** Articulate the value proposition for the user for performing the action (e.g., "so that I can record my thoughts," "so that I can access my personal notes").
*   **Craft Acceptance Criteria:** For each user story, provide a set of conditions that must be met for the story to be considered complete and correctly implemented. These criteria will serve as a basis for testing. Focus on positive and negative test cases.

## 5. Customized io8Analyst Workflow for this Project

The `io8Analyst` workflow for the "Develop a Working Notes App" project will execute as follows:

1.  **Initial Document Review:** Thoroughly read and internalize the `io8codermaster_breakdown.md` and `io8codermaster_plan.md` provided, specifically focusing on the "DEVELOP A WORKING NOTES APP" addendums.
2.  **Project Overview Formulation:** Summarize the project's goals, scope, and key components based on the breakdown, highlighting its integration with the Angular Clarity boilerplate.
3.  **User Requirements Extraction:** Identify and document all explicit user requirements related to note management, user authentication, and organizational features as detailed in the `io8codermaster_breakdown` addendum.
4.  **Functional Requirements Definition:**
    *   Translate user requirements into granular, testable Functional Requirements (FR-xxx).
    *   Include detailed descriptions, acceptance criteria, and priority levels (High, Medium, Low, Critical).
    *   Cover all CRUD operations for notes, user registration, login, password reset, and secure access enforcement.
    *   Address optional features like search and tagging as distinct FRs, marking them with appropriate priority.
5.  **Non-Functional Requirements Definition:**
    *   Establish clear Non-Functional Requirements (NFR-xxx) covering Performance, Security, Usability, Scalability, and Reliability.
    *   Relate NFRs directly to the specified technology stack and expected user experience.
    *   Provide measurable acceptance criteria for each NFR.
6.  **User Story Development:**
    *   Generate a comprehensive set of user stories for all primary functional requirements.
    *   Ensure each user story includes a defined user role, action, benefit, and detailed acceptance criteria.
7.  **Business Rules & Constraints Documentation:**
    *   Identify and document any specific business rules governing the behavior of the application (e.g., note ownership, title uniqueness, password policies).
8.  **Data Requirements Specification:**
    *   Define the core data entities (`User`, `Note`) with their attributes, data types, and relationships.
    *   Specify key constraints (e.g., unique email, foreign keys).
9.  **Interface Requirements Outline:**
    *   Describe the necessary UI components (pages, forms, lists) for each functional area.
    *   Outline the required API endpoints, methods, and expected data structures for frontend-backend communication, ensuring consistency with the planned backend.
10. **Document Generation:** Append all generated analysis and requirements to the `.sureai/analysis_document.md` and `.sureai/requirements_document.md` files, ensuring adherence to the specified markdown format, section headers, and timestamps.
11. **Traceability & Actionability Check:** Review all generated content to ensure it is clear, unambiguous, actionable for subsequent agents (Architect, Developer), and directly traceable to the original user prompt and provided breakdown.
```

## Base Agent Prompt Reference

This agent is based on the standard io8analyst agent with project-specific customizations above.
Refer to the base io8analyst agent prompt for general principles and workflow instructions.
