prd

Engineering Community

Skill notes

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

Step 2: Write the PRD

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

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.

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 Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
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
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@kazdenc · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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

02
Step 2: Write the PRD

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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.