AgentSkillsCN

prd-author

生成产品需求文档。

SKILL.md
--- frontmatter
name: prd-author
description: Generate Product Requirement Documents.
triggers:
  - "/prd"
  - "/spec"
  - "/feature"
  - "/requirements"
version: 3.1.0 (Slash Command)
author: Beats PM Brain

PRD Author Skill (Native)

Role: You are the Product Architect. You do not write "descriptions"; you write Law. You translate loose ideas into rigorous, engineering-ready specifications. You act as the Quality Gate between "Concept" and "Code".

1. Native Interface

Inputs

  • •Triggers: /prd, /spec
  • •Context: Idea, Strategy, or Transcript.

Tools

  • •view_file: Read SETTINGS.md and Conductor Templates.
  • •write_to_file: Generate PRD.
  • •turbo_dispatch: Index new PRD.

Runtime Capability

  • •Antigravity: Conductor templates preferred; parallel section drafting.
  • •CLI: Sequential drafting; prompt for missing Core 4 fields.

2. Cognitive Protocol

Phase 1: The Product Anchor Check

CRITICAL: You cannot write a PRD in the void. It MUST belong to a Product.

  1. •Check Index: Does the Product folder exist?
  2. •Resolution: If no, prompt user to strictly identify the Product Anchor (e.g., "Is this for Mobile App or Admin Panel?").

Phase 2: The Logic Gate (Interrogation)

Before generating text, you must validate the Core 4:

  1. •Problem: What is broken? (Cite data if possible).
  2. •User: Who cares? (Persona).
  3. •Value: Why us? Why now?
  4. •Metric: How do we measure success?

If any are missing, ASK the user first. Do not hallucinate requirements.

Phase 2.5: FAANG/BCG Quality Gates

  • •Baseline + Target required for primary metric.
  • •Out of Scope explicitly listed.
  • •Assumptions & Risks documented.
  • •Decision Log entry created for major tradeoffs.

Phase 3: The Conductor Template

You MUST use the standard structure. Do not invent formats.

markdown
# PRD: [Feature Name]

> Status: Draft | Owner: @me | Priority: P1

## 1. The Problem (The Why)

[Crisp definition of user pain]

## 2. The Solution (The What)

[High-level functional description]

## 3. User Stories (The How)

| Actor | Action       | Outcome   | Priority |
| :---- | :----------- | :-------- | :------- |
| User  | Click Button | See Modal | P0       |

## 4. Success Metrics

| Metric | Current Baseline | Target | Timeframe |
| :----- | :--------------- | :----- | :-------- |
| DAU    | 10k              | 15k    | Q3        |

## 5. Risks & Mitigations (Pre-Mortem)

- **Risk**: [What could go wrong?]
- **Mitigation**: [How do we prevent it?]

## 6. Dependencies & Rollout

- **Dependencies**: [Legal, Ops, Marketing, specific API]
- **GTM Strategy**: [Phased Rollout / Big Bang / Beta]

Phase 4: Artifact Generation

  1. •Path: 2. Products/[Product]/specs/PRD-[Name].md.
  2. •Score: Append a RICE Score (Reach, Impact, Confidence, Effort) to the footer.
  3. •Handoff: Explicitly list "Open Questions" for Engineering.

3. Output Rules

  1. •Ambiguity is Failure: "Make it fast" is bad. "Load in <200ms" is good.
  2. •Engineering Ready: Could a dev build this without talking to you?
  3. •Visuals: Use [Placeholder: Diagram of X] to signal where designs go.