plan-and-analyze

Generate a traceable PRD from project documentation and interview data.

1|1|Updated Dec 30, 2025

Search Tags:#requirements #discovery #interviews #traceability #prd #context-ingestion #plan-and-analyze

Ready to run

npx skills add https://github.com/0xHoneyJar/loa-constructs --skill plan-and-analyze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-and-analyze
Source: https://github.com/0xHoneyJar/loa-constructs/tree/main/.claude/skills/discovering-requirements
Command: npx skills add https://github.com/0xHoneyJar/loa-constructs --skill plan-and-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the discovery and documentation of product requirements by grounding PRDs in existing code and contextual documents.

Core Features & Use Cases

Ingests context and project documentation from grimoires/loa/context to reveal gaps and ambiguities
Conducts a structured 7-phase interview to elicit requirements and validate understanding
Generates a fully traceable PRD at grimoires/loa/prd.md with explicit source citations

Quick Start

Run the skill to generate a fully traced PRD by first placing context docs in grimoires/loa/context and then invoking the plan-and-analyze workflow.

Frequently Asked Questions about plan-and-analyze

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

FAQPage Schema

How do I generate a PRD grounded in existing project documentation?▼

The plan-and-analyze workflow ingests existing project documentation from grimoires/loa/context to reveal gaps and ambiguities, then generates a production-ready PRD with traceable citations.

What is interview-driven requirements discovery for product management?▼

Interview-driven requirements discovery uses a structured 7-phase process to elicit requirements, validate understanding, and extract gaps from ingested context, ultimately synthesizing them into a PRD.

How do I ensure traceability in a product requirements document?▼

You ensure PRD traceability by generating the document via a synthesis process that maps explicit sources, producing grimoires/loa/prd.md with traceable citations linking back to the original context.

Do I need to prepare context files before generating requirements documentation?▼

Yes, you must place existing project documentation and grounding data into the grimoires/loa/context directory before invoking the workflow to ensure accurate requirements extraction.

What's the best way to extract gaps and ambiguities from project context?▼

The best way to extract gaps is by ingesting project documentation to reveal ambiguities, followed by a structured 7-phase interview to validate understanding and define explicit requirements.