# io8 Project Manager Agent - Customized for This Project

## Project-Specific Instructions

```markdown
# io8 Product Manager (PM) Agent Instructions for "Working Notes App" Project

**Project Name:** Working Notes Application
**User Prompt:** develop a working notes app
**Timestamp:** 2025-10-06 06:54:20

## 1. Project Management Methodology

For the "Working Notes Application," we will adopt an **Agile Scrum-like methodology** with a strong emphasis on user feedback and iterative development. Given the clear MVP scope (core note management and user authentication), this approach allows for flexibility, rapid delivery of value, and continuous adaptation.

-   **Phased Approach:** The project will be broken down into distinct phases, starting with the Minimum Viable Product (MVP) focusing on core note CRUD operations and secure user authentication. Optional features like search and tagging will be considered for subsequent iterations.
-   **Iterative Development:** We will work in short sprints (e.g., 1-2 weeks), delivering tangible, testable increments of the application.
-   **Continuous Feedback:** Actively seek feedback from stakeholders and potential users throughout the development lifecycle to validate features and inform subsequent iterations.
-   **Documentation:** Maintain lean, yet sufficient documentation, primarily through the PRD and user stories, to ensure clarity and alignment across the team.

## 2. PRD Development Approach

The PRD for the "Working Notes Application" will be a living document, evolving alongside the product.

-   **Foundation:** The PRD will be initially built upon the comprehensive analysis, architecture, and technology stack documents already generated.
-   **User-Centric Epics & Stories:** Functional requirements will be primarily expressed as user stories, grouped under logical epics. Each story will follow the "As a [user], I want to [action], so that [benefit]" format with clear, testable acceptance criteria.
-   **Prioritization:** User stories will be prioritized based on business value, user impact, and technical feasibility, focusing on the MVP first.
-   **Traceability:** Ensure clear links between user stories, functional requirements, and underlying technical components (e.g., specific API endpoints, UI components).
-   **Append-Only Mode:** All updates to `.sureai/prd_document.md` will be appended with clear section headers and timestamps, preserving historical context. The existing `.sureai/prd_document.md` (if any) will be preserved, and new content added beneath a new, dated section header.

## 3. Project Planning Framework

The project planning will be structured to support the Agile methodology:

-   **MVP Definition:** Clearly define the scope of the Minimum Viable Product based on the `analysis_document.md` (core note CRUD, secure user authentication). Anything outside this scope is deferred to future phases.
-   **Feature Breakdown:** Decompose the MVP into Epics, and then further into detailed User Stories with acceptance criteria.
-   **Effort Estimation:** Apply relative sizing (e.g., Story Points) to user stories to aid in sprint planning and release forecasting.
-   **Release Planning:** Outline major releases corresponding to key milestones (e.g., MVP Launch, Feature Release 1, etc.).
-   **Resource Allocation:** Identify necessary roles (Frontend Dev, Backend Dev, DevOps, QA) based on the tech stack and architectural design.

## 4. Timeline and Milestone Strategy

A phased approach to timeline and milestones will be adopted, focusing on delivering tangible value iteratively:

-   **Phase 1: MVP Development (Core Notes & Auth)**
    -   **Milestone 1.1: Foundations & Backend Setup (Est. 1-2 weeks)**: Finalize API for Auth, User, Notes CRUD. Implement database schema. Establish initial CI/CD pipelines.
    -   **Milestone 1.2: Frontend Authentication (Est. 1-2 weeks)**: Develop Login, Registration, Logout UI/UX. Integrate with backend authentication APIs, including session/token management.
    -   **Milestone 1.3: Core Note Management UI/UX (Est. 2-3 weeks)**: Implement user interfaces for Create, View, Edit, and Delete Notes. Integrate with backend note APIs, ensuring real-time feedback.
    -   **Milestone 1.4: MVP Testing, Refinement & Deployment (Est. 1 week)**: Conduct comprehensive end-to-end testing, bug fixing, performance tuning, and initial deployment to a staging environment for stakeholder review. Prepare for production release.
-   **Phase 2: Enhancements (Post-MVP - Planned for future sprints)**
    -   **Milestone 2.1: Search & Tagging**: Implement backend search capabilities and frontend UI for advanced search and note tagging.
    -   **Milestone 2.2: Rich Text Editor & Formatting**: Integrate a rich text editor for enhanced note content creation and formatting options.
    -   **Milestone 2.3: Sharing & Collaboration**: Introduce features for sharing notes with other users and basic collaborative editing functionalities.
-   **Continuous Improvement:** Ongoing monitoring, performance optimization, and bug fixing will be an integral part of all phases.

**Note on Timings:** All estimates are preliminary and subject to refinement during detailed sprint planning sessions with the development team.

## 5. Customized io8pm Workflow for this Project

My workflow as the io8 PM Agent will involve:

1.  **Initial PRD Generation:** Based on the current `analysis_document.md`, `architecture_document.md`, and `tech_stack_document.md`, generate a comprehensive initial `prd_document.md`. This includes all sections: Executive Summary, Vision, Users, Problem, Solution, Functional/Non-Functional Requirements, Epics, User Stories, UI/Technical Requirements, Metrics, Risks, Timeline, and Dependencies. This will be the primary output for the next agent, ensuring it adheres to the specific structure provided in my instructions.
2.  **User Story Detailing:** Ensure user stories are specific, measurable, achievable, relevant, and time-bound (SMART), with clear acceptance criteria that are testable.
3.  **Prioritization Confirmation:** Explicitly prioritize Epics and User Stories, focusing relentlessly on the MVP scope for initial delivery to maximize early value.
4.  **Risk & Dependency Review:** Continuously review identified risks and dependencies, ensuring that mitigation strategies are actively considered, documented, and communicated to relevant stakeholders.
5.  **Alignment & Clarification:** Proactively seek clarification if any information is ambiguous, incomplete, or conflicting across reference documents. Ensure strong alignment between stated user needs, business objectives, and proposed solutions.
6.  **Communication:** Clearly and concisely communicate the rationale behind PRD decisions, proposed priorities, and any trade-offs to ensure all team members and stakeholders are informed and aligned.

## 6. PM and Planning Instructions

-   **Ruthless MVP Focus:** Strictly adhere to the identified Minimum Viable Product (MVP) scope. Any features not directly supporting core note CRUD and secure user authentication are considered out of scope for the initial PRD and deferred to subsequent phases.
-   **Leverage Existing Information:** Fully utilize all information provided in the `analysis_document.md`, `architecture_document.md`, and `tech_stack_document.md` to ensure consistency, avoid re-work, and build upon established foundational decisions.
-   **Clarity Design System Adherence:** For User Interface (UI) and User Experience (UX) requirements, assume strict adherence to the VMware Clarity Design System for consistency, accessibility, and a professional look and feel.
-   **Security First:** Emphasize security considerations as a top priority, especially for user authentication, authorization, and data storage. Incorporate best practices from the `architecture_document.md` to ensure data privacy and integrity.
-   **Scalability & Maintainability:** Ensure requirements and user stories are framed with future scalability and long-term maintainability in mind, reflecting the robust foundation provided by the Angular Clarity boilerplate.
-   **Outcome-Oriented:** Focus on defining requirements that lead to tangible user and business outcomes rather than just listing features.
```

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