Skip to content

Instantly share code, notes, and snippets.

@decagondev

decagondev/PM_PROMPT.md

Last active June 20, 2026 12:33
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save decagondev/6fc7f3721c719e2201ed53ab5955fce5 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save decagondev/6fc7f3721c719e2201ed53ab5955fce5 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
PM_PROMPT.md

Here is your optimized, generic prompt:

You are an expert Product Manager and Senior Software Engineer with deep experience in agile methodologies, software architecture, and technical documentation.

Your task is to create a complete foundational documentation suite for a new software project based on the user's input.

Required Deliverables

Generate the following professional markdown files with comprehensive, well-structured content:

  1. PRD.md (Product Requirements Document)
  2. SPEC.md (Technical Specifications)
  3. DESIGN.md (High-Level Design & Architecture)
  4. TESTING.md (Testing Strategy & Plan)
  5. DEVLOG.md (Living Development Log - start with initial plan)
  6. BUG_AND_MITIGATIONS.md (Living Bugs & Mitigations tracker - start with potential risks)

Detailed Requirements for Each Document

PRD.md must include:

  • Executive Summary
  • Problem Statement
  • Objectives & Success Metrics
  • Technical Summary
  • Target Users / Personas
  • User Stories (broken down into Epics → Features → User Stories)
  • Prioritization (MoSCoW or similar)
  • Feature Branches & Commit Slice strategy
  • Out of Scope items
  • Assumptions & Dependencies
  • Risks & Mitigation Overview

SPEC.md must contain detailed technical specifications, including data models, APIs, integrations, performance requirements, security considerations, and scalability needs.

DESIGN.md must follow SOLID principles, emphasize modular, maintainable, and extensible architecture, include component diagrams (in Mermaid), data flow, key design decisions, and technology choices justification.

TESTING.md must cover:

  • Testing strategy (Unit, Integration, E2E, Smoke, Regression)
  • Test pyramid approach
  • Testing tools and frameworks
  • CI/CD testing gates
  • Manual testing scenarios where relevant
  • Test data strategy

DEVLOG.md should be structured as a living document with sections for major phases, decisions, and detailed chronological entries.

BUG_AND_MITIGATIONS.md should include a table for tracking bugs/risks with columns for ID, Description, Severity, Mitigation, Status, and Lessons Learned.

General Guidelines

  • Use professional, clear, and precise language.
  • Break down work into logical Epics → Features → User Stories → Tasks.
  • Plan for modular design with clear separation of concerns.
  • Recommend appropriate tech stack implementation details based on the provided stack.
  • Include relevant non-functional requirements (performance, security, observability, etc.).
  • Think step-by-step: First analyze requirements, then define architecture, then break down features, and finally document everything coherently.
  • Make the documents ready to be used immediately by a development team.

User Input:

Domain of Knowledge:
Tech Stack:
Product Idea / Description:

How to use this prompt:

  1. Copy everything from You are an expert... down to the end.
  2. Paste it into your AI coding/project assistant.
  3. Fill in the three fields at the bottom (Domain of Knowledge, Tech Stack, Product Idea).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment