# io8 Project Manager Agent - Customized for This Project

## Project-Specific Instructions

## 1. Executive Summary
[2025-09-24T13:15:00] Updated Executive Summary:
This document outlines the Product Requirements Document (PRD) for a notes-taking application. The application will allow users to create, edit, delete, search, and organize their notes using tags.  It will support rich text editing, file attachments, and optional cloud synchronization (future phase). The application leverages an existing Angular Clarity boilerplate, extending its functionality to meet these specific needs.

## 2. Product Vision & Strategy
[2025-09-24T13:16:00] Updated Product Vision & Strategy:
**Product Vision:** To create a simple, intuitive, and secure notes-taking application that empowers users to capture and organize their thoughts and ideas effectively.
**Strategic Goals:**
- Develop a Minimum Viable Product (MVP) with core note-taking functionality within [Timeframe - e.g., 4 weeks].
- Ensure the application is responsive and user-friendly across various devices.
- Implement robust security measures to protect user data.
- Prioritize a clean, well-documented codebase.
**Success Metrics:**
- Number of registered users.
- Average session duration.
- Number of notes created per user.
- User satisfaction rating (based on surveys/feedback).

## 3. Target Users & Personas
[2025-09-24T13:17:00] Updated Target Users & Personas:
**Persona 1: The Student**
- Age: 18-25
- Occupation: Student
- Needs: Easy-to-use note-taking app for lectures, assignments, and studying. Needs organization features (tags). May not need cloud sync immediately.

**Persona 2: The Professional**
- Age: 25-45
- Occupation: Professional (various fields)
- Needs: Secure and reliable note-taking app for meeting notes, project plans, and client communication. Needs search and organization features, as well as cloud sync for accessibility across devices.

## 4. Problem Statement
[2025-09-24T13:18:00] Updated Problem Statement:
Many existing note-taking applications lack a combination of features crucial for effective note management: seamless rich text editing, secure data storage, intuitive organization, and efficient search capabilities.  This application aims to address these issues by providing a user-friendly, feature-rich solution.

## 5. Solution Overview
[2025-09-24T13:19:00] Updated Solution Overview:
A responsive web application built on the Angular Clarity Boilerplate.  The application will provide a clean and intuitive user interface for creating, editing, deleting, and organizing notes.  Core features include rich text editing, tagging, file attachments, and search functionality.  User authentication and authorization will be implemented to secure user data.

## 6. Functional Requirements
[2025-09-24T13:20:00] Updated Functional Requirements:
- **FR-001:** Create a new note with title, content, tags, and optional attachments.
- **FR-002:** Edit an existing note (title, content, tags, attachments).
- **FR-003:** Delete a note.
- **FR-004:** Search notes by title and content using keywords.
- **FR-005:** Organize notes using tags.
- **FR-006:** Support rich text editing (bold, italic, headings, lists, links).
- **FR-007:** Allow attachments (images, documents).
- **FR-008:** Implement secure user authentication and authorization.
- **FR-009:**  Implement user profile management.

## 7. Non-Functional Requirements
[2025-09-24T13:21:00] Updated Non-Functional Requirements:
- **NFR-001:** Responsive design across devices.
- **NFR-002:** High performance and minimal loading times.
- **NFR-003:** Secure data storage and transmission (HTTPS, encryption).
- **NFR-004:** Intuitive and user-friendly interface.
- **NFR-005:** Scalable architecture to handle a growing number of users and notes.

## 8. Epic Stories
[2025-09-24T13:22:00] Updated Epic Stories:
### Epic 1: Core Note-Taking Functionality
**Epic Description:** Implement the core features for creating, editing, deleting, and searching notes.
**Business Value:** Provides the fundamental functionality of the notes-taking application.
**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 and content so I can save my thoughts and ideas.
  - **Acceptance Criteria:**  A new note is created with a title and content.  The note is saved and can be retrieved.
  - **Story Points:** 5
  - **Priority:** High
- **US-002:** As a user, I want to edit an existing note so I can update my information.
  - **Acceptance Criteria:**  The note is updated and the changes are saved.
  - **Story Points:** 3
  - **Priority:** High
- **US-003:** As a user, I want to delete a note so I can remove unwanted information.
  - **Acceptance Criteria:** The note is deleted and cannot be retrieved.
  - **Story Points:** 2
  - **Priority:** High
- **US-004:** As a user, I want to search for notes using keywords in the title and content so I can quickly find what I need.
  - **Acceptance Criteria:** Search returns relevant notes based on keywords.
  - **Story Points:** 8
  - **Priority:** High

### Epic 2: Note Organization and Rich Text Editing
**Epic Description:** Implement features for organizing notes using tags and enabling rich text editing.
**Business Value:** Improves user experience and organization.
**Acceptance Criteria:**  All user stories within this epic are completed and tested.

**User Stories:**
- **US-005:** As a user, I want to use tags to organize my notes so I can easily manage my notes.
  - **Acceptance Criteria:** Notes can be tagged with multiple tags. Search and filtering by tags works correctly.
  - **Story Points:** 5
  - **Priority:** Medium
- **US-006:** As a user, I want to use rich text editing features (bold, italic, headings, lists, links) in my notes to improve readability.
  - **Acceptance Criteria:** Rich text formatting options are available and function correctly.
  - **Story Points:** 7
  - **Priority:** Medium

### Epic 3: User Authentication and Authorization
**Epic Description:** Implement secure user authentication and authorization.
**Business Value:** Protects user data and ensures security.
**Acceptance Criteria:**  Secure user login and registration are implemented. Unauthorized access is prevented.

**User Stories:**
- **US-007:** As a user, I want to create an account so I can save my notes securely.
  - **Acceptance Criteria:** User registration works correctly.
  - **Story Points:** 8
  - **Priority:** High
- **US-008:** As a user, I want to log in securely to access my notes.
  - **Acceptance Criteria:** User login works correctly.  JWT is used for authentication.
  - **Story Points:** 7
  - **Priority:** High

## 9. User Interface Requirements
[2025-09-24T13:23:00]  Updated User Interface Requirements:
- Clean, modern design consistent with the Clarity Design System.
- Intuitive navigation and user flow.
- Responsive layout adaptable to various screen sizes.
- Clear visual feedback for user interactions.

## 10. Technical Requirements
[2025-09-24T13:24:00] Updated Technical Requirements:
- Frontend: Angular, TypeScript, Clarity Design System, RxJS, Quill.js (rich text editor), HttpClient.
- Backend: Node.js with Express.js (or Python with Django/Flask) - RESTful API, JWT authentication, MongoDB (or PostgreSQL).
- Database: MongoDB (or PostgreSQL).

## 11. Success Metrics & KPIs
[2025-09-24T13:25:00] Updated Success Metrics & KPIs:
- Number of registered users
- Number of notes created
- Average session duration
- User engagement (time spent in the app)
- User retention rate
- Customer satisfaction score (CSAT)

## 12. Risk Assessment
[2025-09-24T13:26:00] Updated Risk Assessment:
- **Risk 1:**  Backend development delays.
  - **Mitigation:** Agile development approach, prioritized tasks, close collaboration between frontend and backend teams.
- **Risk 2:**  Security vulnerabilities.
  - **Mitigation:**  Regular security testing, secure coding practices, input validation.
- **Risk 3:**  Lack of user adoption.
  - **Mitigation:**  Marketing and user feedback incorporation.

## 13. Timeline & Milestones
[2025-09-24T13:27:00] Updated Timeline & Milestones:
- **Week 1:**  Backend API setup and initial database design.
- **Week 2:**  Frontend development of core note-taking features.
- **Week 3:**  Implementation of rich text editor, tagging, and search functionality.
- **Week 4:**  User authentication and authorization, testing, and deployment of MVP.

## 14. Dependencies & Assumptions
[2025-09-24T13:28:00] Updated Dependencies & Assumptions:
- Existing Angular Clarity Boilerplate is functional and provides a solid base.
- Backend development team is available and resources are sufficient.
- Adequate testing time is allocated.

[2025-09-24T13:30:00] Project Plan Update:
This section outlines the project plan for the notes-taking application.  The plan incorporates an agile methodology, focusing on iterative development and continuous feedback.

**1. Project Initiation:**
- Define project scope and objectives.
- Assemble project team.
- Establish communication channels.

**2. Planning:**
- Create a detailed project plan using a work breakdown structure (WBS).
- Define tasks, dependencies, and timelines.
- Allocate resources and assign roles.
- Determine success criteria.

**3. Execution:**
- Develop the application in iterations (sprints) of [Duration - e.g., 2 weeks].
- Conduct daily stand-up meetings for progress tracking.
- Conduct sprint reviews and retrospectives for continuous improvement.
- Address impediments and make necessary adjustments.

**4. Monitoring & Controlling:**
- Monitor progress against the project plan regularly.
- Track risks and issues.
- Report progress to stakeholders.
- Manage changes and make adjustments as needed.

**5. Closure:**
- Conduct a final project review.
- Document lessons learned.
- Archive project materials.

**Agile Methodology:** The project will follow an Agile methodology, specifically Scrum.  This will involve:
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective

**Risk Management:**
- Regularly assess potential risks and challenges.
- Develop contingency plans to mitigate risks.
- Track and monitor risks throughout the project lifecycle.

**Communication Plan:**
- Establish regular communication channels (e.g., daily stand-up meetings, weekly email updates, Slack).
- Communicate project status to stakeholders regularly.
- Ensure timely and effective communication across the team.

**Timeline:** The project is estimated to take [Total Time - e.g., 4 weeks], with major milestones defined in the PRD.

**Tools:**
- Project management software (e.g., Jira, Asana, Trello).
- Version control system (Git).
- Communication platform (e.g., Slack).

**Team Roles:**
- Product Manager
- Frontend Developers
- Backend Developers
- QA Tester


## 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.
