Interview users to generate structured PRDs with traceability tables.
npx skills add https://github.com/lshtram/core_dev --skill spec-writer-lshtram
Please help me install this Agent Skill. Skill: spec-writer Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/spec-writer Command: npx skills add https://github.com/lshtram/core_dev --skill spec-writer-lshtram
This skill guides structured interviews to crystallize vague requests into a complete Product Requirements Document (PRD), reducing ambiguity and alignment overhead.
Start a feature request by interviewing me and generating a complete PRD saved as docs/PRD_[FeatureName].md using the included PRD_TEMPLATE.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from a vague idea, an interview-based process clarifies the request by guiding discovery questions. It captures goals, user stories, and constraints, then fills a structured PRD template to crystallize your product requirements.
The best way to structure requirements and traceability is using a PRD template that includes a dedicated Traceability section. This maps requirements directly to verification criteria, preparing a structured draft ready for stakeholder review.
Writing product requirements for early-stage features across diverse domains involves answering discovery questions to define goals and user stories. The process outputs a standardized PRD document with success criteria and traceability mapping.
Interview-based product requirement generation works without prior technical documentation by relying on guided discovery questions. It extracts goals and constraints directly from your responses to build a complete PRD from scratch.
You can automate PRD template usage to generate a markdown file saved as docs/PRD_[FeatureName].md. The process fills the template sections directly from interview answers to create a ready-to-review document.
HerbertJulioTranslate product ideas into structured PRDs with user stories and GitHub issues.
hyperjumptechConvert PRDs into implementation tickets with acceptance criteria and traceability.
konglong87Convert PRD requirements into user stories with BDD acceptance criteria.
tiweenCreate and validate Product Requirement Documents through structured interviews and stakeholder alignment.
