prd

Engineering Community

Repo stars 38
License MIT
Author repo builder-skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Write a product requirements document from context. Covers problem statement, goals, scope, user stories, success criteria, and…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Step 1: Gather Context”, “Step 2: Write the PRD”, “Problem Statement”, “Goals & Non-Goals”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name prd directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Step 1: Gather Context / Step 2: Write the PRD / Problem Statement” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Product Requirements Document

Write a PRD that answers two questions clearly: what are we building and why does it matter. Everything else is supporting detail.

Step 1: Gather Context

Before writing anything, nail down these three inputs. If the user hasn't provided them, ask.

Input	Question	Watch out for
Problem	What pain exists today? Who feels it?	Jumping to solutions before the problem is sharp
Audience	Who specifically benefits? What's their situation?	"Everyone" is not an audience
Current state	How do people solve this now? What's broken?	Assuming nothing exists today

If a JTBD analysis, research, or prior conversations exist, pull from them. Don't invent context.

Step 2: Write the PRD

Use this structure. Every section earns its place — skip a section only if it genuinely doesn't apply.

# PRD: [Feature / Product Name]

## Problem Statement
What's broken, missing, or painful. Ground it in real user behavior.
Who has this problem. How often. How bad.

## Goals & Non-Goals

### Goals
- [ ] Measurable outcome this work achieves
- [ ] Another measurable outcome

### Non-Goals
- What this work deliberately does NOT try to solve (and why)

## User Stories / Job Stories
Use job story format when possible:
- When [situation], I want to [motivation], so I can [outcome]

Keep to 3-8 stories. If you have more, the scope is too big.

## Functional Requirements
What the system must do. Number them for traceability.

FR-1: [Requirement]
FR-2: [Requirement]

## Non-Functional Requirements
Performance, security, accessibility, scale, compatibility.

NFR-1: [Requirement]
NFR-2: [Requirement]

## Success Metrics
How we'll know this worked. Be specific:
- Metric + target + timeframe
- e.g., "Reduce average onboarding time from 12 min to under 5 min within 30 days of launch"

## Open Questions
What's unresolved. Who owns answering it. When it needs an answer by.

| # | Question | Owner | Deadline |
|---|----------|-------|----------|

## Out of Scope
What's explicitly excluded from this effort. Prevents scope creep later.

Quality Checks

Run these before delivering the PRD:

Every requirement is testable. If you can't write a pass/fail check for it, rewrite it. "Fast" is not testable. "Loads in under 2 seconds on 3G" is.
No solutions hiding as requirements. "Use Redis for caching" is a solution. "Cache frequently accessed data with sub-100ms retrieval" is a requirement.
Scope is realistic. If the PRD has 30+ requirements, it's a roadmap pretending to be a PRD. Split it.
Goals are measurable. Each goal should have a number attached or a clear yes/no test.
Non-goals are deliberate. They prevent future arguments about what "should have been included."
Open questions have owners. An open question without an owner is a stalled decision.

Tone and Format

Write requirements as imperative statements: "The system shall..." or "Users can..."
Use numbered identifiers (FR-1, NFR-1) so engineers and designers can reference them
Keep the language concrete. Replace "intuitive" with observable behavior. Replace "scalable" with specific numbers.
One requirement per line. Compound requirements hide complexity.

When the PRD Is Done

Hand it off with three things clear:

What's decided — requirements that are locked
What's open — questions that still need answers
What's next — who reviews, who builds, what's the timeline

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Engineering
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @kazdenc · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview prd.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Product Requirements Document

Write a PRD that answers two questions clearly: **what are we building** and **why does it matter**. Everything else is supporting detail.

## Step 1: Gather Context

Before writing anything, nail down these three inputs. If the user hasn't provided them, ask.

| Input | Question | Watch out for |
|-------|----------|---------------|
| **Problem** | What pain exists today? Who feels it? | Jumping to solutions before the problem is sharp |
| **Audience** | Who specifically benefits? What's their situation? | "Everyone" is not an audience |
| **Current state** | How do people solve this now? What's broken? | Assuming nothing exists today |

If a JTBD analysis, research, or prior conversations exist, pull from them. Don't invent context.

## Step 2: Write the PRD

Use this structure. Every section earns its place — skip a section only if it genuinely doesn't apply.

```
# PRD: [Feature / Product Name]

## Problem Statement
What's broken, missing, or painful. Ground it in real user behavior.
Who has this problem. How often. How bad.

## Goals & Non-Goals

### Goals
- [ ] Measurable outcome this work achieves
- [ ] Another measurable outcome

### Non-Goals
- What this work deliberately does NOT try to solve (and why)

## User Stories / Job Stories
Use job story format when possible:
- When [situation], I want to [motivation], so I can [outcome]

Keep to 3-8 stories. If you have more, the scope is too big.

## Functional Requirements
What the system must do. Number them for traceability.

FR-1: [Requirement]
FR-2: [Requirement]

## Non-Functional Requirements
Performance, security, accessibility, scale, compatibility.

NFR-1: [Requirement]
NFR-2: [Requirement]

## Success Metrics
How we'll know this worked. Be specific:

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Step 1: Gather Context → Step 2: Write the PRD → Problem Statement → Goals & Non-Goals → Goals → Non-Goals
terms    -> what are we building · why does it matter · Problem · Audience · Current state · Every requirement is testable. · No solutions hiding as requirements. · Scope is realistic.
files/cmd -> pass/fail · yes/no
body sha256 -> 650f15942a4a