All skills
asyrafhussin avatar

/prd-writing

@eaaf04f

Step-by-step workflow for writing Product Requirements Documents. Use when creating PRDs, documenting features, writing specifications, or planning new products. Triggers on "write PRD", "create PRD", "document requirements", "feature spec", or "product requirements".

Use this Skill: https://skilld.dev/gh/asyrafhussin/agent-skills/prd-writing

This session only. Nothing lands on disk.

rulesstruct-executive-summary.md

≈617 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Write a Concise Executive Summary

Impact: CRITICAL (First thing stakeholders read — sets the tone)

The executive summary is a single paragraph (3-5 sentences) that captures the problem, proposed solution, and expected impact. A busy stakeholder should understand the entire PRD from this section alone.

Incorrect

<!-- Bad: too long, too vague, solution-focused -->
## Executive Summary

We are going to build a URL shortening service. This will involve
creating a new database table, a controller, views for CRUD operations,
and an analytics dashboard. We'll use Laravel for the backend and
React for the frontend. The project will take approximately 4 weeks.
We need this because competitors have it. The service will support
custom slugs, expiry dates, SEO metadata, and click tracking with
geolocation. We'll also need admin functionality for user management.
Redis might be useful for caching. We should consider rate limiting too.

Problems:

  • Reads like a feature list, not a summary
  • No problem statement
  • No measurable impact
  • Implementation details don't belong here
  • Too long — loses the reader

Correct

<!-- Good: problem → solution → impact in one paragraph -->
## Executive Summary

Marketing teams currently share long, unbranded URLs that reduce
click-through rates by 23% compared to short, branded links (source:
Q4 analytics). We propose a self-hosted URL shortening service that
allows authenticated users to create trackable short links with
custom slugs, expiry dates, and SEO metadata. Success is measured by
achieving >90% adoption among marketing team members within 30 days
and a 15% improvement in campaign click-through rates.

Benefits:

  • Problem is clear in the first sentence
  • Solution is specific but not prescriptive
  • Impact is measurable and time-bound
  • Entire PRD context in 4 sentences

Why

  1. Respects reader time: Executives and stakeholders skim — give them the essence upfront
  2. Forces clarity: If you can't summarize it in a paragraph, you don't understand it well enough
  3. Enables quick decisions: Approvers can say yes/no based on the summary alone
  4. Sets evaluation criteria: The impact statement becomes the benchmark for success

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides a structured workflow and comprehensive best practices for writing Product Requirements Documents (PRDs). It guides the agent through discovery, stakeholder alignment, and technical specification drafting. No malicious code, exfiltration patterns, or injection attempts were found.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at eaaf04f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
metadata
{
  "author": "agent-skills",
  "version": "1.0.0"
}

README badge

README badge for asyrafhussin/agent-skills/prd-writing