# io8 Project Manager Agent - Customized for This Project

## Project-Specific Instructions

## 1. Executive Summary
Generated: 2025-09-24 07:45:00
This document outlines the product requirements for a "notess" application, a simple note-taking application designed for ease of use and intuitive design.  The application will allow users to create, edit, save, and search notes locally, initially focusing on a frontend-only implementation with the possibility of backend integration in future iterations.

## 2. Product Vision & Strategy
Generated: 2025-09-24 07:45:00
The vision for "notess" is to become a user-friendly and efficient note-taking tool.  The initial strategy focuses on a minimum viable product (MVP) featuring core note-taking functionalities.  Future iterations may include features such as collaboration, synchronization, and advanced organization capabilities.

## 3. Target Users & Personas
Generated: 2025-09-24 07:45:00
**Persona 1: The Student**
- Needs a simple way to take notes during lectures and study sessions.
- Values ease of use and quick access to notes.

**Persona 2: The Professional**
- Needs a tool to jot down ideas, meeting notes, and task lists.
- Values organization and the ability to quickly search notes.

**Persona 3: The Casual User**
- Needs a simple, no-frills way to record quick thoughts and reminders.
- Values simplicity and ease of use above all else.

## 4. Problem Statement
Generated: 2025-09-24 07:45:00
Current note-taking solutions are often overly complex, cluttered, or lack basic functionality.  Many applications require accounts, synchronization, or other features that are not necessary for basic note-taking.  "notess" addresses this problem by providing a streamlined, intuitive, and locally-focused note-taking experience.

## 5. Solution Overview
Generated: 2025-09-24 07:45:00
"notess" is a single-page application (SPA) built using Angular and the Clarity Design System, providing a consistent and modern user interface.  The application will offer core note-taking functionalities including creation, editing, saving, searching, and deleting notes. Data will be persistently stored locally using IndexedDB to ensure offline capabilities.  Future iterations may expand to include richer text formatting, advanced search, and potentially cloud synchronization.

## 6. Functional Requirements
Generated: 2025-09-24 07:45:00
- **FR-001:** Users shall be able to create new notes with rich text formatting (bold, italic, lists).
- **FR-002:** Users shall be able to edit existing notes with rich text formatting.
- **FR-003:** Users shall be able to save notes persistently using IndexedDB.
- **FR-004:** Users shall be able to search for notes using keywords with partial matching.
- **FR-005:** Users shall be able to view their saved notes with proper formatting.
- **FR-006:** Users shall be able to delete notes.

## 7. Non-Functional Requirements
Generated: 2025-09-24 07:45:00
- **NFR-001:** The application shall be intuitive and easy to use.
- **NFR-002:** The application shall be responsive and performant.
- **NFR-003:** The application shall protect user data (via secure local storage).
- **NFR-004:** The application shall function offline.

## 8. Epic Stories
Generated: 2025-09-24 07:45:00
### Epic 1: Core Note-Taking Functionality
**Epic Description:** Implement the core features for creating, editing, saving, searching, and deleting notes.
**Business Value:** Provides the basic functionality of the application.
**Acceptance Criteria:** All functional requirements (FR-001 to FR-006) are met.

**User Stories:**
- **US-001:** As a user, I want to create a new note so that I can capture my thoughts and ideas.
  - **Acceptance Criteria:**  A new note can be created and saved. Text is stored correctly.
  - **Story Points:** 5
  - **Priority:** High
- **US-002:** As a user, I want to edit an existing note so that I can correct mistakes and add more information.
  - **Acceptance Criteria:**  Existing notes can be loaded, edited, and saved. Rich text formatting is preserved.
  - **Story Points:** 8
  - **Priority:** High
- **US-003:** As a user, I want to save my notes persistently so that my work is not lost.
  - **Acceptance Criteria:**  Notes are saved to IndexedDB and retrieved correctly after closing and reopening the browser.
  - **Story Points:** 10
  - **Priority:** High
- **US-004:** As a user, I want to search for notes using keywords so that I can find specific information quickly.
  - **Acceptance Criteria:**  A search function correctly finds notes containing the specified keywords, partial matches are supported.
  - **Story Points:** 8
  - **Priority:** High
- **US-005:** As a user, I want to view my saved notes so that I can access my previous work.
  - **Acceptance Criteria:**  Notes are displayed correctly, rich text formatting is preserved.
  - **Story Points:** 5
  - **Priority:** High
- **US-006:** As a user, I want to delete notes so that I can remove unwanted content.
  - **Acceptance Criteria:**  Notes can be deleted from the list and the database.
  - **Story Points:** 3
  - **Priority:** High

### Epic 2: Rich Text Formatting
**Epic Description:** Implement rich text formatting capabilities for notes.
**Business Value:** Enhances user experience and note-taking functionality.
**Acceptance Criteria:** Bold, italic, and bulleted list formatting are supported.

**User Stories:**
- **US-007:** As a user, I want to format my notes using bold, italics, and lists so that my notes are easier to read and organize.
  - **Acceptance Criteria:**  Rich text formatting is applied correctly and persisted.
  - **Story Points:** 13
  - **Priority:** Medium

## 9. User Interface Requirements
Generated: 2025-09-24 07:45:00
The UI should be clean, intuitive, and consistent with the Clarity Design System.  Wireframes and mockups will be developed during the design phase.

## 10. Technical Requirements
Generated: 2025-09-24 07:45:00
- Frontend: Angular, Clarity Design System, ngx-quill (rich text editor), IndexedDB
- Offline functionality

## 11. Success Metrics & KPIs
Generated: 2025-09-24 07:45:00
- User engagement (time spent in app, number of notes created).
- User satisfaction (feedback surveys).

## 12. Risk Assessment
Generated: 2025-09-24 07:45:00
- Risk: Issues with IndexedDB performance or compatibility.
  - Mitigation: Thorough testing and fallback mechanisms.

## 13. Timeline & Milestones
Generated: 2025-09-24 07:45:00
- **Milestone 1 (Week 1):** Complete core functionality (Epic 1).
- **Milestone 2 (Week 2):** Implement rich text formatting (Epic 2).
- **Milestone 3 (Week 3):** Testing and bug fixes.
- **Milestone 4 (Week 4):** Deployment.

## 14. Dependencies & Assumptions
Generated: 2025-09-24 07:45:00
- Assumption:  Developers have sufficient Angular experience.
- Dependency:  Selection of a suitable rich text editor library.

## Project Plan Update - 2025-09-24 07:50:00

### Project Methodology:
The project will utilize an Agile Scrum methodology with two-week sprints.  This will allow for iterative development and flexibility to adapt to changing requirements.

### PRD Development Approach:
The PRD will be iteratively refined throughout the project, with updates made after each sprint based on feedback and progress.

### Project Planning Framework:
- **Sprint Planning:** At the start of each sprint, the team will identify the user stories to be completed.
- **Daily Stand-ups:**  Daily short meetings to discuss progress and identify roadblocks.
- **Sprint Review:** At the end of each sprint, the team will present the completed work and gather feedback.
- **Sprint Retrospective:**  The team will review the process and identify areas for improvement.

### Timeline and Milestone Strategy:
- **Sprint 1 (Week 1-2):** Focus on core note-taking functionalities (Epic 1).  Milestone:  MVP with core functionalities.
- **Sprint 2 (Week 3-4):**  Implement rich text formatting (Epic 2).  Milestone:  Rich text editing is functional.
- **Sprint 3 (Week 5-6):**  Testing, bug fixes, and UI improvements.  Milestone:  Beta release.
- **Sprint 4 (Week 7-8):** Deployment and initial user feedback gathering.  Milestone:  Production release.

### Customized io8pm Workflow:
1. **Review Documents:** Thoroughly review the analysis document, architecture document, and technology stack document.
2. **Refine PRD:** Update the PRD based on the analysis and design documentation, ensuring alignment between requirements and technical feasibility.
3. **Create Project Plan:** Develop a detailed project plan with tasks, timelines, and responsibilities.
4. **Risk Management:** Identify and document potential project risks and mitigation strategies.
5. **Communication:**  Maintain consistent communication with the development team and stakeholders.
6. **Monitoring and Control:** Track progress, manage changes, and ensure the project stays on schedule and within budget.
7. **Iteration and Feedback:**  Integrate regular feedback from the development team and users into the project plan and PRD.

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