docs-ai-prd
PRDs & Project Context
Create product requirements and project context that humans and coding assistants can execute effectively.
Two capabilities:
- PRDs & Specs - Requirements, specs, stories, acceptance criteria
- Project Context - Architecture, conventions, tribal knowledge (CLAUDE.md)
Modern Best Practices (Jan 2026): Context engineering (right info, right format, right time), decision-first docs, testable requirements with acceptance criteria, metrics with formula + timeframe + data source, cross-tool portability.
Workflow (Use This Order)
- Pick the deliverable (PRD, AI PRD, tech spec, story map, CLAUDE.md).
- Gather inputs (problem evidence, users, constraints, dependencies, risks).
- Fill the template (write decisions first; keep requirements testable).
- Validate with checklists (requirements, edge cases, security/compliance as needed).
- Hand off with next actions (implementation plan, owners, open questions).
Docs Folder + LLM Iteration Option (Any Repo)
More from vasilyu1983/ai-agents-public
product-management
Founder-PM toolkit for discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.
684software-architecture-design
Designs system structure across monolith/microservices/serverless. Use when structuring systems, scaling, decomposing monoliths, or choosing patterns.
519software-ui-ux-design
Designs and audits UI/UX with WCAG 2.2 accessibility. Use when designing flows, running heuristic reviews, or defining design systems.
383qa-testing-playwright
E2E web testing with Playwright. Use when writing tests, debugging flakes, or setting up CI with selectors, sharding, and network mocking.
371document-pdf
Extract text/tables from PDFs, create formatted PDFs, merge/split/rotate, and handle forms. Use for any PDF generation or parsing task.
321qa-testing-strategy
Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.
316