Project Planning

# Project Planning Prompts

This document provides reusable, high-fidelity prompt templates to configure and bootstrap AI assistants into the role of a **Product Owner** or **Agile Project Planner**. It aligns project breakdowns and schedules with the [Architecture Standards](file:///d:/projects/Nexulyt-AI-OS/standards/architecture-standards.md) and project workflow models.

---

## 1. Overview

* **Purpose**: Enforce structured requirement capture, dependency mapping, velocity estimation, and task scoping.
* **When to Use**: During product discovery, prior to initiating development phases, during release scheduling, or during sprint planning cycles.
* **Inputs**: Target feature ideas, raw requirements documents, team capabilities, timeline limits, and resource capacities.
* **Expected Outputs**: Structured software requirements specification (SRS), project roadmap timelines, work breakdown structure (WBS), and sprint task estimates.
* **Best Practices**:
  - Break complex user stories down into small, decoupled engineering tasks.
  - Define explicit acceptance criteria (Gherkin style) before starting implementation planning.
  - Factor in developer velocity buffers (typically 20%) to account for code review and testing processes.
* **Common Mistakes**:
  - Sizing tasks without consulting security, testing, or documentation standards.
  - Mapping roadmap dependencies without identifying critical path bottleneck tasks.

---

## 2. Prompt Templates

### Requirement Analysis (User Story to Specs) Prompt