product-requirements

Translate ambiguous project requirements into testable PRDs saved to docs/{feature-name}-prd.md.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill product-requirements-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/product-requirements
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill product-requirements-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague requirements into clear, testable Product Requirements Documents (PRDs), reducing ambiguity and rework in product planning.

Core Features & Use Cases

  • Quality-driven requirement shaping: applies a 100-point scoring framework to evaluate business value, scope, UX, and technical constraints.
  • PRD generation: converts validated requirements into a structured PRD stored at docs/{feature-name}-prd.md.
  • Iterative refinement: supports rounds of stakeholder clarification to reach a 90+ quality score before generation.

Quick Start

Describe your feature concept with enough context and I will generate a professional PRD draft saved to docs/{feature-name}-prd.md.

Frequently Asked Questions about product-requirements

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

FAQPage Schema
How do I turn vague feature concepts into a structured PRD?

A PRD quality framework evaluates business value, functional requirements, user experience, technical constraints, and scope using a 100-point scoring system to reduce ambiguity and rework across multiple stakeholders.

How do I write user stories from ambiguous project requirements?

To generate a PRD, describe your feature concept with enough context to trigger iterative refinement rounds, which validate requirements against a 90+ quality score before saving the final document to docs/{feature-name}-prd.md.

What is a 100-point quality framework for product requirements documents?

A PRD quality framework evaluates business value, functional requirements, user experience, technical constraints, and scope using a 100-point scoring system to reduce ambiguity and rework across multiple stakeholders.

How do I generate a PRD from a feature concept using stakeholder validation?

To generate a PRD, describe your feature concept with enough context to trigger iterative refinement rounds, which validate requirements against a 90+ quality score before saving the final document to docs/{feature-name}-prd.md.

Can I assess business value and technical constraints for multiple use cases in one PRD?

Stakeholder clarification is required to reach a 90+ quality score on the 100-point framework before final PRD generation, ensuring all business value, UX, and technical constraints are fully validated.