factory-prd

Guide structured interviews to define product requirements in EARS format.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JongHyunLee84/factory --skill factory-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-prd
Source: https://github.com/JongHyunLee84/factory/tree/main/skills/factory-prd
Command: npx skills add https://github.com/JongHyunLee84/factory --skill factory-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses common failures in requirements definition, such as assumption-based writing, solutions without problem definition, and ambiguous requirements, by enforcing a structured interview process.

Core Features & Use Cases

  • Structured Interviewing: Guides users through a mandatory interview process to uncover needs.
  • Value Hypothesis Formulation: Ensures that the "why" behind a feature is clearly defined and falsifiable.
  • EARS Pattern Enforcement: Mandates the use of the Event-driven, Actor-driven, Role-driven, and System-driven (EARS) format for all requirements.
  • Use Case: A product manager needs to define requirements for a new feature. They use this Skill to conduct interviews, ensuring all assumptions are validated, the value proposition is clear, and requirements are documented in the EARS format before handing off to the development team.

Quick Start

Use the factory-prd skill to start a new product requirements document by answering the initial interview questions.

Frequently Asked Questions about factory-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write product requirements using the EARS format?

The EARS format structures product requirements into Event-driven, Actor-driven, Role-driven, and System-driven categories. Using a structured interview process ensures requirements are unambiguous and validated before development handoff.

How do I avoid writing product requirements based on unvalidated assumptions?

To avoid assumption-based product requirements, use a mandatory interview-driven process to uncover actual user needs. This ensures every requirement is tied to a validated problem and a falsifiable value hypothesis before documentation.

What is the best way to structure a product requirements document for a new feature?

The best way to structure a product requirements document is combining a structured interview protocol with a standard product manager PRD layout. This enforces clear problem definition and EARS-formatted requirements.

How do I conduct a requirements interview to define user stories?

Conduct a requirements interview by following a structured, interview-then-plan protocol to extract user stories and needs. This prevents solutions without clear problem definition and ensures all assumptions are validated.

When do I need to use a structured interview process for product management?

You need a structured interview process for product management when defining requirements for a new feature to prevent ambiguous documentation. It enforces the EARS format and ensures value hypotheses are falsifiable before development.