swe-prd

Generate Product Requirements Documents as Markdown files from codebase context.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/MmtBkn/swe --skill swe-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-prd
Source: https://github.com/MmtBkn/swe/tree/main/swe-prd
Command: npx skills add https://github.com/MmtBkn/swe --skill swe-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates the creation of Product Requirements Documents (PRDs) or proposals, transforming feature ideas into structured, actionable documents that align teams and guide development.

Core Features & Use Cases

  • Automated PRD Generation: Creates PRDs based on user prompts and codebase context.
  • Contextual Awareness: Reads existing product context and codebase structure to inform the PRD.
  • Structured Output: Generates PRDs in a standardized Markdown format with clear sections.
  • Use Case: When you have a new feature idea, use this Skill to generate a comprehensive PRD that outlines the problem, scope, requirements, and user experience, ensuring everyone is aligned before development begins.

Quick Start

Use the swe-prd skill to create a product requirements document for a new user authentication feature.

Frequently Asked Questions about swe-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a product requirements document from an existing codebase?

To generate a product requirements document from an existing codebase, this skill analyzes your product context, codebase architecture, and deployment details to automatically create a structured PRD in Markdown format.

What is the best way to write a feature definition that aligns my development team?

The best way to write a feature definition for team alignment is to create a PRD that clearly answers the 'what' and 'why' of the product, rather than the 'how', ensuring everyone understands the scope before development begins.

Can I create a testable proposal without specifying the technical implementation details?

Yes, you can create a testable proposal without specifying technical implementation details because this skill defines product features by answering 'what' and 'why', ensuring the generated requirements remain comprehensive and clear for development teams.

How do I structure product requirements as Markdown files within my repository?

To structure product requirements as Markdown files within your repository, this skill outputs standardized documents into a specified repository structure, organizing the problem, scope, requirements, and user experience into clear sections.

Does automated PRD generation work with existing deployment details and architecture?

Automated PRD generation works with existing deployment details and architecture by reading your current codebase structure and product context to inform the resulting comprehensive, testable requirements document.