discovering-requirements

Generate Product Requirements Documents with source traceability from documentation and interviews.

4|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/loa-hounfour --skill discovering-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovering-requirements
Source: https://github.com/0xHoneyJar/loa-hounfour/tree/main/.claude/skills/discovering-requirements
Command: npx skills add https://github.com/0xHoneyJar/loa-hounfour --skill discovering-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs) by intelligently synthesizing existing documentation and conducting targeted interviews, ensuring all requirements are grounded in source material.

Core Features & Use Cases

  • Contextual Synthesis: Ingests and analyzes documentation from specified directories (grimoires/loa/context/) before asking questions.
  • Gap Identification: Pinpoints missing information and ambiguities in provided context.
  • Targeted Interviewing: Asks precise, focused questions only for uncovered areas.
  • Codebase Grounding (Brownfield): Integrates with codebase analysis tools (/ride) to ensure PRDs reflect actual code reality.
  • Source Tracing: Generates PRDs with explicit citations linking every requirement back to its origin (document, code, or interview).
  • Use Case: A product manager needs to create a PRD for a new feature. They place existing design docs, user research, and technical notes into the grimoires/loa/context/ directory. The Skill analyzes these, identifies gaps in functional requirements and success metrics, and asks targeted questions to fill those gaps, ultimately producing a fully traceable PRD.

Quick Start

Use the discovering-requirements skill to create a PRD for a new feature by placing your existing documentation in the grimoires/loa/context/ directory and then invoking the skill.

Frequently Asked Questions about discovering-requirements

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

FAQPage Schema
How do I generate a PRD from existing project documentation?

To generate a PRD, place your existing design docs and technical notes into the context directory. The skill analyzes these materials, identifies missing functional requirements, and asks targeted interview questions to produce a fully traceable PRD.

Can I create product requirements for a brownfield project based on the actual codebase?

Yes, brownfield projects are supported through codebase analysis integration. The skill grounds product requirements in actual code reality, ensuring the generated PRD accurately reflects the existing system architecture and constraints.

How does the product discovery process handle missing information in user research?

The discovery process identifies gaps and ambiguities in your provided context. Instead of guessing, it conducts targeted interviews by asking precise questions only for uncovered areas to fill in the missing information.

What is the best way to trace PRD requirements back to their original source?

Source tracing is built directly into the PRD generation process. Every requirement in the final document includes explicit citations linking it back to its origin, whether that source is an interview, a document, or code.

Does requirements gathering work with large volumes of project context and documentation?

Yes, the skill handles large context volumes through parallel processing. It supports phased discovery, allowing you to systematically synthesize extensive documentation without overwhelming the analysis pipeline.