# io8 Project Manager Agent - Customized for This Project

## Project-Specific Instructions

# Product Requirements Document (PRD) Update - 2025-09-24T[TIMESTAMP]

## 1. Executive Summary Update
This update to the PRD focuses on the addition of a notes-taking application, leveraging the existing Angular Clarity Boilerplate as a foundation. The application will allow users to create, edit, delete, search, and organize their notes with rich text editing, attachment support, and optional cloud synchronization.

## 2. Product Vision & Strategy Update
The notes-taking application aims to provide a user-friendly and efficient platform for capturing and managing personal notes.  The key strategy is to leverage the existing Angular Clarity Boilerplate for rapid development and maintain consistency with the organization's design system.

## 3. Target Users & Personas Update
The target users are individuals seeking a simple yet powerful notes application for personal use. Key features will cater to individual preferences, including rich text editing, attachment support, and tag-based organization.

## 4. Problem Statement Update
The existing Angular Clarity Boilerplate project has provided a sound base, but the need for a notes-taking application functionality was not addressed before. This PRD aims to address the user need to create, organize, and easily access personal notes effectively.

## 5. Solution Overview Update
The solution will be a single-page application (SPA) built using Angular, leveraging the existing Clarity Design System and built as a feature module within the existing application's structure. The architecture will incorporate microservices for scalability and maintainability.  Key features include rich text editing, attachment handling, tagging, and optional cloud synchronization.

## 6. Functional Requirements Update
The following functional requirements are added for the notes-taking application:

- **FR-011: Note Creation:** The system shall allow users to create new notes with a title, content, tags, and optional attachments.
- **FR-012: Note Editing:** The system shall allow users to edit existing notes, including title, content, tags, and attachments.
- **FR-013: Note Deletion:** The system shall allow users to delete notes.
- **FR-014: Note Search:** The system shall allow users to search notes by title and content using keywords.
- **FR-015: Note Tagging:** The system shall allow users to add multiple tags to notes for organization.
- **FR-016: Rich Text Editing:** The system shall provide a rich text editor (e.g., Quill.js) for formatted note content.
- **FR-017: Attachment Management:** The system shall support attaching files (images, documents) to notes.
- **FR-018: Cloud Synchronization (Future):** The system shall optionally allow users to synchronize their notes to a cloud service.
- **FR-019: Offline Access (Future):** The system shall allow users to access and edit notes offline, with synchronization upon reconnection.
- **FR-020: User Authentication:**  The system shall integrate with existing user authentication mechanisms.

## 7. Non-Functional Requirements Update
- **NFR-005: Performance:** The application shall be responsive and performant, with minimal loading times.
- **NFR-006: Security:** User data shall be protected with appropriate security measures (encryption, authorization).
- **NFR-007: Usability:** The application shall be intuitive and user-friendly.
- **NFR-008: Scalability:** The application shall be scalable to handle a growing number of users and notes.

## 8. Epic Stories Update

### Epic 1: Note Management
**Epic Description:**  Enable users to create, edit, delete, and manage their notes.
**Business Value:** Provides core note-taking functionality.
**Acceptance Criteria:** All user stories within this epic are completed and tested.

**User Stories:**
- **US-001:** As a user, I want to create a new note with a title, content, and tags, so I can save my ideas and thoughts.
  - **Acceptance Criteria:**  A new note is successfully created and saved.
  - **Story Points:** 8
  - **Priority:** High
- **US-002:** As a user, I want to edit an existing note, so I can update information and correct mistakes.
  - **Acceptance Criteria:** Existing notes can be modified, and updates are saved successfully.
  - **Story Points:** 5
  - **Priority:** High
- **US-003:** As a user, I want to delete notes, so I can keep my workspace organized.
  - **Acceptance Criteria:** Notes can be deleted permanently.
  - **Story Points:** 3
  - **Priority:** Medium

### Epic 2: Note Search and Organization
**Epic Description:** Allow users to search for notes and organize them using tags.
**Business Value:** Improves note retrieval and management.
**Acceptance Criteria:** Search functionality is implemented with tag-based filtering.

**User Stories:**
- **US-004:** As a user, I want to search for notes using keywords, so I can quickly find information.
  - **Acceptance Criteria:** Search results are relevant and accurate, filtering notes by title and content.
  - **Story Points:** 10
  - **Priority:** High
- **US-005:** As a user, I want to organize notes using tags, so I can easily manage my notes.
  - **Acceptance Criteria:** Notes can be tagged with multiple tags, and notes can be filtered by tags.
  - **Story Points:** 6
  - **Priority:** High

### Epic 3: Rich Text Editing and Attachments
**Epic Description:** Enhance note-taking experience with rich text formatting and file attachments.
**Business Value:** Improves note creation and information organization.
**Acceptance Criteria:** Rich text editing and file attachments are supported.

**User Stories:**
- **US-006:** As a user, I want to use rich text formatting (bold, italic, headings, lists), so I can create visually appealing and organized notes.
  - **Acceptance Criteria:** Rich text formatting features are implemented and work correctly.
  - **Story Points:** 12
  - **Priority:** High
- **US-007:** As a user, I want to attach files (images, documents) to my notes, so I can keep all relevant information together.
  - **Acceptance Criteria:** Files can be attached and displayed correctly.
  - **Story Points:** 8
  - **Priority:** High

## 9. User Interface Requirements Update
[Update UI requirements to reflect the new features. Consider adding wireframes or mockups]

## 10. Technical Requirements Update
[Update technical requirements to reflect the use of microservices, MongoDB, and other technologies]

## 11. Success Metrics & KPIs Update
[Define metrics for user engagement, note creation, search effectiveness, and user satisfaction]

## 12. Risk Assessment Update
[Identify potential risks related to microservices architecture, database scalability, and cloud integration]

## 13. Timeline & Milestones Update
[Update project timeline to include the new features.  Define milestones for each epic]

## 14. Dependencies & Assumptions Update
[Update dependencies and assumptions to reflect the new technical stack and integration points]

# Project Plan Update - 2025-09-24T[TIMESTAMP]

## Project Management Methodology
This project will employ an Agile methodology using Scrum, with two-week sprints.  Daily stand-up meetings will keep the team synchronized, and sprint reviews will ensure alignment with the PRD.  A Kanban board will be used to visualize work progress and manage tasks.

## PRD Development Approach
The PRD will be iteratively updated throughout the project, incorporating feedback from the development team and stakeholders.  The initial PRD will focus on core features, with future iterations including cloud synchronization and offline capabilities.

## Project Planning Framework
The project will be broken down into epics and user stories as outlined in the PRD.  Tasks will be assigned to developers, and progress will be tracked using a project management tool.

## Timeline and Milestone Strategy
**Phase 1 (4 weeks):** Core note-taking functionality (creation, editing, deletion, basic search).
    - **Milestone 1:**  Complete user authentication integration.
    - **Milestone 2:**  Implement note creation, editing, and deletion functionality.
    - **Milestone 3:**  Develop basic search functionality.

**Phase 2 (2 weeks):** Enhancements (rich text editing, attachments, tagging).
    - **Milestone 4:**  Integrate a rich text editor.
    - **Milestone 5:**  Implement attachment handling.
    - **Milestone 6:**  Implement note tagging and filtering by tag.

**Phase 3 (4 weeks):** Cloud synchronization and offline access (future phases).
    - **Milestone 7:**  Complete cloud integration (database synchronization).
    - **Milestone 8:**  Implement offline access capabilities.

## Customized io8pm Workflow
1. **Requirements Gathering and Analysis:**  Review the PRD and all relevant documents.  Clarify any ambiguities or gaps in requirements.
2. **Project Planning:**  Create a detailed project plan outlining tasks, timelines, and milestones. Define sprint goals and user stories.
3. **Sprint Execution:**  Manage sprints using an Agile methodology, conducting daily stand-ups, sprint reviews, and retrospectives.
4. **Risk Management:**  Identify and mitigate risks proactively, creating contingency plans for potential issues.
5. **Stakeholder Communication:**  Keep stakeholders informed of progress, challenges, and decisions.
6. **Monitoring and Reporting:**  Track progress against the project plan, creating regular reports for stakeholders. 
7. **Quality Assurance:** Ensure thorough testing of all features and functionality.
8. **Deployment:**  Coordinate and oversee the deployment process.
9. **Post-Launch Monitoring:** Monitor application performance and user feedback post-launch.

## Specific Instructions for Subsequent Agents
- **io8codermaster:**  Focus on microservices architecture design and implementation.  Utilize Node.js and Express.js for API development, MongoDB for data persistence, and potentially Elasticsearch for the search service.  Develop robust unit and integration tests.
- **io8tester:**  Develop a comprehensive testing strategy for all features and components.  Include unit tests, integration tests, and end-to-end (E2E) tests using Cypress.
- **io8deployer:**  Design and implement a CI/CD pipeline using a suitable platform (GitHub Actions, GitLab CI, etc.).  Develop automated deployment scripts for cloud hosting.



## Base Agent Prompt Reference

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