gds-edit-prd

Edit PRDs to improve clarity, structure, and measurability.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill gds-edit-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-edit-prd
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-edit-prd
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-edit-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD editing often lacks structure and measurable criteria. This skill provides a BMAD-guided, repeatable process to discover, plan, and execute PRD improvements.

Core Features & Use Cases

  • Guided discovery of user edit requirements
  • BMAD/legacy format detection and routing
  • Validation report integration for prioritized improvements
  • Stepwise change planning, approval, and execution
  • Seamless handoff to downstream artifacts (UX, Architecture)

Quick Start

Provide the PRD path and your edit goals, and I will guide you through discovery, planning, and execution.

Frequently Asked Questions about gds-edit-prd

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

FAQPage Schema
How do I edit a PRD to improve clarity and add measurable criteria?

Editing a PRD for clarity and measurability requires a structured workflow that discovers edit requirements, detects document format, and executes stepwise changes. This ensures documentation improvements are planned, validated, and tracked properly through frontmatter compliance.

What is the BMAD standard for product requirements documentation?

The BMAD standard is a structured documentation format that enforces clarity, measurable criteria, and frontmatter tracking. It routes legacy documents into a compliant structure by integrating validation reports and coordinating stepwise improvements.

How do I update a legacy PRD to meet current validation standards?

Updating a legacy PRD involves detecting the legacy format, integrating a validation report to prioritize improvements, and creating a stepwise change plan. This routing ensures old documents adopt compliant structures and measurable criteria.

Can I plan and approve PRD changes step by step before execution?

Yes, you can plan and approve PRD changes step by step. A guided workflow coordinates discovery, generates a stepwise change plan, secures approval, and then executes the edits while maintaining frontmatter tracking and BMAD compliance.

How do I hand off a completed PRD to UX and architecture teams?

Handing off a completed PRD requires a structured workflow that finalizes edits, satisfies frontmatter tracking, and enables seamless downstream artifact generation. This ensures validated requirements transfer cleanly to subsequent UX and architecture planning phases.