One-click install
npx skills add https://github.com/SpaceZephyr/allSkills --skill space-prd-writer-spacezephyr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SPACE-prd-writer
Source: https://github.com/SpaceZephyr/allSkills/tree/main/pm-prd-writer
Command: npx skills add https://github.com/SpaceZephyr/allSkills --skill space-prd-writer-spacezephyr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams frequently face misalignment, rework, and delayed reviews due to unstructured, incomplete product requirement documents (PRDs) derived from vague, fragmented initial requirements. This Skill eliminates that pain point by standardizing the process of converting rough ideas, meeting notes, chat screenshots, or unpolished requirement descriptions into formal, executable PRDs that align all cross-functional stakeholders.

Core Features & Use Cases

  • 4-Stage Structured Workflow: Follows a clear Clarify → Structure → Enrich → Deliver process to ensure no critical requirement gaps are missed during PRD creation.
  • Automatic Gap-Filling: Proactively adds missing edge case handling, tracking scheme definitions, non-functional requirements, and system integration details to PRDs to improve completeness.
  • Fallback for Underdeveloped Requirements: When key requirement information is insufficient, outputs a requirement breakdown document instead of a half-baked PRD to avoid wasted development effort.
  • Use Case: Ideal for product managers who need to quickly convert rough requirements from business stakeholders, meeting minutes, or informal chats into formal, reviewable PRDs for development and design teams, or optimize existing incomplete PRDs.

Quick Start

Use the SPACE-prd-writer skill to turn your rough feature idea and associated meeting notes into a complete, review-ready product requirement document.

Frequently Asked Questions about SPACE-prd-writer

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

FAQPage Schema
How do I turn vague requirements into a structured product requirement document?

To turn vague requirements into a structured product requirement document, use a 4-stage workflow that clarifies, structures, enriches, and delivers fragmented inputs into a review-ready PRD.

What is the best way to draft a PRD from meeting notes and informal chats?

The best way to draft a PRD from meeting notes and informal chats is applying an automatic gap-filling process that adds missing edge cases, tracking schemes, and non-functional requirements.

How do I ensure cross-functional alignment before a PRD review?

You ensure cross-functional alignment before a PRD review by standardizing requirement definitions and proactively filling system integration gaps to reduce rework from incomplete documents.

What happens when initial product requirements are too underdeveloped for a PRD?

When initial product requirements are too underdeveloped for a PRD, the system outputs a requirement breakdown document instead of a half-baked PRD to avoid wasted development effort.

Can I use this workflow to optimize an existing incomplete PRD?

Yes, you can use this workflow to optimize an existing incomplete PRD by processing the unpolished requirement descriptions through the structured enrichment stages to achieve full executability.