# io8 Project Manager Agent - Customized for This Project

## Project-Specific Instructions

## 1. Executive Summary

[2025-09-25T10:03:00] This document outlines the product requirements for a notes-taking application. The application will allow users to create, edit, delete, search, tag, and organize their notes.  Further details regarding platform (web, mobile, desktop), data storage (local, cloud), and authentication will be determined in subsequent phases.

## 2. Product Vision & Strategy

[2025-09-25T10:03:00] The vision is to create a user-friendly and efficient notes-taking application that helps users effectively manage and organize their information.  The strategy will focus on iterative development, starting with a Minimum Viable Product (MVP) that includes core note management features, followed by progressive enhancements based on user feedback.

## 3. Target Users & Personas

[2025-09-25T10:03:00]  The target users are individuals who need a simple and efficient way to take and organize notes.  Personas will be developed in a subsequent phase to represent various user types and their specific needs.

## 4. Problem Statement

[2025-09-25T10:03:00] Existing note-taking solutions may lack features for efficient organization, search, and portability across devices.  This application aims to address these shortcomings by providing a user-friendly interface with robust organization and search capabilities.

## 5. Solution Overview

[2025-09-25T10:03:00]  The application will provide a platform for creating, editing, deleting, searching, tagging, and organizing notes.  Users will be able to organize notes into notebooks and apply tags for efficient searching and retrieval.  The initial MVP will focus on core functionality, with later phases potentially incorporating features such as user authentication, cloud synchronization, and rich text editing.

## 6. Functional Requirements

[2025-09-25T10:03:00]
- **FR-001: Create a new note:** Users should be able to create notes with text content.
- **FR-002: Edit an existing note:** Users should be able to modify the content of existing notes.
- **FR-003: Delete a note:** Users should be able to remove notes.
- **FR-004: Search for notes:** Users should be able to search notes by keyword (title and content).
- **FR-005: Tag a note:** Users should be able to add tags to notes for organization.
- **FR-006: Organize notes into notebooks:** Users should be able to create and assign notes to notebooks.
- **FR-007: Export notes:** Users should be able to export notes in plain text format (.txt).

## 7. Non-Functional Requirements

[2025-09-25T10:03:00]
- **NFR-001: User-friendliness:** The application should be intuitive and easy to use.
- **NFR-002: Performance:** The application should be responsive and performant, even with a large number of notes.
- **NFR-003: Reliability:** The application should be reliable and stable.
- **NFR-004: Security (MVP):**  Security requirements for the MVP are minimal, focusing on input validation and sanitization. More robust security features will be added in later phases if user authentication is implemented.

## 8. Epic Stories

### Epic 1: Core Note Management
**Epic Description:** This epic encompasses the core functionality of creating, editing, deleting, searching, and organizing notes.
**Business Value:** Provides the foundational features necessary for basic note-taking functionality.
**Acceptance Criteria:** All user stories within this epic are completed and tested.

**User Stories:**
- **US-001: Create a New Note**
  - **As a** user
  - **I want to** create a new note with a title and content
  - **So that** I can save my thoughts and ideas
  - **Acceptance Criteria:**
    - [ ] A new note is successfully created with the provided title and content.
    - [ ] The new note is saved locally and can be retrieved later.
  - **Story Points:** 5
  - **Priority:** High

- **US-002: Edit an Existing Note**
  - **As a** user
  - **I want to** edit an existing note
  - **So that** I can correct mistakes or add new information
  - **Acceptance Criteria:**
    - [ ] An existing note can be edited.
    - [ ] The edited note is saved locally.
  - **Story Points:** 3
  - **Priority:** High

- **US-003: Delete a Note**
  - **As a** user
  - **I want to** delete an existing note
  - **So that** I can remove unwanted information
  - **Acceptance Criteria:**
    - [ ] An existing note can be deleted.
    - [ ] The deleted note is removed from the list of notes.
  - **Story Points:** 2
  - **Priority:** High

- **US-004: Search Notes**
  - **As a** user
  - **I want to** search for notes using keywords
  - **So that** I can quickly find the notes I need
  - **Acceptance Criteria:**
    - [ ] A search function exists and returns relevant notes based on keywords in title and content.
    - [ ] Search is case-insensitive.
  - **Story Points:** 8
  - **Priority:** High

- **US-005: Add Tags to Notes**
  - **As a** user
  - **I want to** add tags to notes
  - **So that** I can categorize and organize my notes
  - **Acceptance Criteria:**
    - [ ] Tags can be added to notes.
    - [ ] Notes can be searched by tags.
  - **Story Points:** 5
  - **Priority:** Medium

- **US-006: Organize Notes into Notebooks**
  - **As a** user
  - **I want to** organize my notes into notebooks
  - **So that** I can group related notes together
  - **Acceptance Criteria:**
    - [ ] Notebooks can be created.
    - [ ] Notes can be assigned to notebooks.
    - [ ] Notes can be searched and filtered by notebook.
  - **Story Points:** 7
  - **Priority:** Medium

- **US-007: Export Notes (txt)**
  - **As a** user
  - **I want to** export my notes as plain text files
  - **So that** I can share or back up my notes
  - **Acceptance Criteria:**
    - [ ] Notes can be exported to a .txt file.
    - [ ] The exported file contains the note's title and content.
  - **Story Points:** 3
  - **Priority:** Medium

### Epic 2: [Future Enhancement - Authentication] (To be defined in subsequent phases)
### Epic 3: [Future Enhancement - Cloud Sync] (To be defined in subsequent phases)

## 9. User Interface Requirements
[2025-09-25T10:03:00]  The UI should be clean, intuitive, and easy to navigate.  Specific UI/UX designs will be developed in a subsequent design phase.

## 10. Technical Requirements
[2025-09-25T10:03:00]  Technical requirements will depend on the chosen platform and backend technologies.  These details will be outlined in subsequent documents.

## 11. Success Metrics & KPIs
[2025-09-25T10:03:00]  Success will be measured by user adoption, user satisfaction, and feature usage.  Specific KPIs will be defined in a subsequent phase.

## 12. Risk Assessment
[2025-09-25T10:03:00]  Risks include the selection of appropriate technologies, meeting deadlines, and ensuring user satisfaction. Mitigation strategies will be developed in a subsequent phase.

## 13. Timeline & Milestones
[2025-09-25T10:03:00] A detailed timeline will be developed in a subsequent phase, outlining key milestones and delivery dates.

## 14. Dependencies & Assumptions
[2025-09-25T10:03:00]  The project depends on the selection of appropriate technologies and the availability of resources. Assumptions include sufficient developer expertise and adequate project funding.

[2025-09-25T10:03:00] This section outlines the project plan for building the notes-taking application.

### Project Management Methodology
[2025-09-25T10:03:00] Agile (Scrum or Kanban) will be used for this project to support iterative development and facilitate quick adaptation to user feedback.

### PRD Development Approach
[2025-09-25T10:03:00]  The PRD will be developed iteratively, with initial focus on core features (MVP), followed by expansion based on user feedback and evolving requirements.

### Project Planning Framework
[2025-09-25T10:03:00]  A Work Breakdown Structure (WBS) will be used to break down the project into manageable tasks, which will be further broken down into user stories.

### Timeline and Milestone Strategy
[2025-09-25T10:03:00]
* **Phase 1 (MVP):** Core note-taking functionality (create, edit, delete, search, tagging). Target completion: 2 weeks.
* **Phase 2:** Notebook organization, note exporting. Target completion: 1 week.
* **Phase 3 (Optional):** User authentication, cloud synchronization (dependent on user feedback and resource availability). Target completion: 4 weeks.

### Customized io8pm Workflow
[2025-09-25T10:03:00] The io8pm workflow will involve close collaboration with the development team to ensure alignment on requirements and address any technical challenges.

1. **Requirements Gathering:** Finalize platform and data storage choices based on user feedback and feasibility.
2. **Design:** Develop UI/UX mockups and designs.
3. **Development (Iterative):** Develop and test the application in phases (MVP first).
4. **Testing:** Conduct rigorous testing at each phase.
5. **Deployment:** Deploy the application to the chosen platform.
6. **Monitoring:** Monitor application performance and gather user feedback.
7. **Iteration:** Iterate based on user feedback and further requirements.

### Risk Mitigation Strategies
[2025-09-25T10:03:00] Risk mitigation strategies will include regular progress meetings, thorough testing, and flexible planning to accommodate unexpected challenges.

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