skill prd

Documentation Community

Skill notes

PHASE 0: CLARIFICATION (MANDATORY)

Before writing ANY PRD content, you MUST ask the user these questions: WAIT for user response before proceeding to Phase 1. If user says "skip" or provides the feature description inline, extract what you can and note assumptions.

PHASE 1: QUICK RESEARCH (Max 2 searches)

Only search if topic is unfamiliar. Limit to 2 web searches max: One for domain/market context One for technical patterns (if needed) Do NOT over-research. 60 seconds max for this phase.

PHASE 2: WRITE PRD

Structure: Executive Summary - Vision + key value prop Problem Statement - Quantified pain points by user segment Goals & Metrics - SMART goals, P0/P1/P2 priority, success metrics table Non-Goals - Explicit boundaries (what we WON'T do)

After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review. A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements. Dispatch the PRD draft to a different provider (Codex, Gemini, or Sonnet as fallback) with this prompt: "Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?"

PHASE 3: SELF-SCORE

Score against 100-point framework: AI-Specific Optimization: 25 pts (sequential phases, non-goals, structured format) Traditional PRD Core: 25 pts (problem statement, goals, personas, specs) Implementation Clarity: 30 pts (FRs with codes, NFRs, architecture, phases) Completeness: 20 pts (risks, dependencies, examples, doc quality)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
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
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

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

01
PHASE 0: CLARIFICATION (MANDATORY)

Before writing ANY PRD content, you MUST ask the user these questions: WAIT for user response before proceeding to Phase 1. If user says "skip" or provides the feature description inline, extract what you can and note assumptions.

02
PHASE 1: QUICK RESEARCH (Max 2 searches)

Only search if topic is unfamiliar. Limit to 2 web searches max: One for domain/market context One for technical patterns (if needed) Do NOT over-research. 60 seconds max for this phase.

03
PHASE 2: WRITE PRD

Structure: Executive Summary - Vision + key value prop Problem Statement - Quantified pain points by user segment Goals & Metrics - SMART goals, P0/P1/P2 priority, success metrics table Non-Goals - Explicit boundaries (what we WON'T do)

04
PHASE 2.5: ADVERSARIAL PRD REVIEW (RECOMMENDED)

After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review. A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements. Dispatch the PRD draft to a different provider (Codex, Gemini, or Sonnet as fallback) with this prompt: "Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?"

05
PHASE 3: SELF-SCORE

Score against 100-point framework: AI-Specific Optimization: 25 pts (sequential phases, non-goals, structured format) Traditional PRD Core: 25 pts (problem statement, goals, personas, specs) Implementation Clarity: 30 pts (FRs with codes, NFRs, architecture, phases) Completeness: 20 pts (risks, dependencies, examples, doc quality)

06
PHASE 4: SAVE

Write to user-specified filename or generate based on feature name. START WITH PHASE 0 CLARIFICATION QUESTIONS NOW.

Discussion

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