{{Project Name}} - Product Requirements Document (PRD)

Generated with JAEGIS Enhanced Validation System

[[LLM: VALIDATION CHECKPOINT - Review shared context from previous agents and validate all inputs. Integrate web research findings and ensure current best practices. If Project Brief available, validate against current market trends.]]

Executive Summary

[[LLM: VALIDATION CHECKPOINT - Provide 2-3 paragraph executive summary based on research and validation. Include market research findings and competitive analysis.]]

Goals and Background Context

[[LLM: VALIDATION CHECKPOINT - Populate sections based on validated inputs and research. Include market validation and competitive analysis. Allow user to review before proceeding.]]

Goals

[[LLM: Research-backed goals with market validation. Each goal should be supported by evidence or market research.]]

  • Primary Goal: {{Primary validated goal with market backing}}

  • Secondary Goals: {{Research-backed secondary goals}}

  • Success Metrics: {{Measurable, validated success criteria}}

Background Context

[[LLM: Include market research and competitive analysis. Reference current market trends and user research findings. 1-2 paragraphs with research citations where applicable.]]

Requirements

[[LLM: Draft the list of functional and non functional requirements under the two child sections, and immediately execute tasks#advanced-elicitation display]]

Functional

[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with FR`.]] @{example: - FR6: The Todo List uses AI to detect and warn against adding potentially duplicate todo items that are worded differently.}

Non Functional

[[LLM: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR`.]] @{example: - NFR1: AWS service usage must aim to stay within free-tier limits where feasible.}

^^CONDITION: has_ui^^

User Interface Design Goals

[[LLM: Capture high-level UI/UX vision to guide Design Architect and to inform story creation. Steps:

  1. Pre-fill all subsections with educated guesses based on project context

  2. Present the complete rendered section to user

  3. Clearly let the user know where assumptions were made

  4. Ask targeted questions for unclear/missing elements or areas needing more specification

  5. This is NOT detailed UI spec - focus on product vision and user goals

  6. After section completion, immediately apply tasks#advanced-elicitation protocol]]

Overall UX Vision

Key Interaction Paradigms

Core Screens and Views

[[LLM: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories]]

@{example}

  • Login Screen

  • Main Dashboard

  • Item Detail Page

  • Settings Page @{/example}

Accessibility: { None, WCAG, etc }

Branding

[[LLM: Any known branding elements or style guides that must be incorporated?]]

@{example}

  • Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.

  • Attached is the full color pallet and tokens for our corporate branding. @{/example}

Target Device and Platforms

@{example} "Web Responsive, and all mobile platforms", "IPhone Only", "ASCII Windows Desktop" @{/example}

^^/CONDITION: has_ui^^

Technical Assumptions

[[LLM: Gather technical decisions that will guide the Architect. Steps:

  1. Check if data#technical-preferences file exists - use it to pre-populate choices

  2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets

  3. For unknowns, offer guidance based on project goals and MVP scope

  4. Document ALL technical choices with rationale (why this choice fits the project)

  5. These become constraints for the Architect - be specific and complete

  6. After section completion, apply tasks#advanced-elicitation protocol.]]

Repository Structure: { Monorepo, Polyrepo, etc...}

Service Architecture

[[LLM: CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).]]

Testing requirements

[[LLM: CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).]]

Additional Technical Assumptions and Requests

[[LLM: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items]]

Epics

[[LLM: First, present a high-level list of all epics for user approval, the epic_list and immediately execute tasks#advanced-elicitation display. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.

CRITICAL: Epics MUST be logically sequential following agile best practices:

  • Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality

  • Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page

  • Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed

  • Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.

  • Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.

  • Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.]]

<<REPEAT: epic_list>>

  • Epic{{epic_number}} {{epic_title}}: {{short_goal}}

<>

@{example: epic_list}

  1. Foundation & Core Infrastructure: Establish project setup, authentication, and basic user management

  2. Core Business Entities: Create and manage primary domain objects with CRUD operations

  3. User Workflows & Interactions: Enable key user journeys and business processes

  4. Reporting & Analytics: Provide insights and data visualization for users

@{/example}

[[LLM: After the epic list is approved, present each epic_details with all its stories and acceptance criteria as a complete review unit and immediately execute tasks#advanced-elicitation display, before moving on to the next epic.]]

<<REPEAT: epic_details>>

Epic {{epic_number}} {{epic_title}}

{{epic_goal}} [[LLM: Expanded goal - 2-3 sentences describing the objective and value all the stories will achieve]]

[[LLM: CRITICAL STORY SEQUENCING REQUIREMENTS:

  • Stories within each epic MUST be logically sequential

  • Each story should be a "vertical slice" delivering complete functionality

  • No story should depend on work from a later story or epic

  • Identify and note any direct prerequisite stories

  • Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.

  • Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.

  • Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow

  • Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained

  • If a story seems complex, break it down further as long as it can deliver a vertical slice

  • Each story should result in working, testable code before the agent's context window fills]]

<<REPEAT: story>>

Story {{epic_number}}.{{story_number}} {{story_title}}

As a {{user_type}}, I want {{action}}, so that {{benefit}}.

Acceptance Criteria

[[LLM: Define clear, comprehensive, and testable acceptance criteria that:

  • Precisely define what "done" means from a functional perspective

  • Are unambiguous and serve as basis for verification

  • Include any critical non-functional requirements from the PRD

  • Consider local testability for backend/data components

  • Specify UI/UX requirements and framework adherence where applicable

  • Avoid cross-cutting concerns that should be in other stories or PRD sections]]

<<REPEAT: criteria>>

  • {{criterion number}}: {{criteria}}

<> <> <>

Change Log

Change

Date

Version

Description

Author

----- END PRD START CHECKLIST OUTPUT ------

Checklist Results Report

[[LLM: Before running the checklist and drafting the prompts, offer to output the full updated PRD. If outputting it, confirm with the user that you will be proceeding to run the checklist and produce the report. Once the user confirms, execute the pm-checklist and populate the results in this section.]]

----- END Checklist START Design Architect UI/UX Specification Mode Prompt ------

Design Architect Prompt

[[LLM: This section will contain the prompt for the Design Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]

----- END Design Architect UI/UX Specification Mode Prompt START Architect Prompt ------

Architect Prompt

[[LLM: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.]]

----- END Architect Prompt ------

PreviousPowerShell Installer TemplateNext{{Project Name}} - Project Brief

Last updated