Transform rough notes into a structured REQUIREMENTS.md document.
npx skills add https://github.com/owainlewis/blueprint --skill requirements-owainlewis
Please help me install this Agent Skill. Skill: requirements Source: https://github.com/owainlewis/blueprint/tree/main/skills/requirements Command: npx skills add https://github.com/owainlewis/blueprint --skill requirements-owainlewis
This Skill transforms unstructured notes into a clear, actionable requirements document, ensuring all stakeholders are aligned before development begins.
REQUIREMENTS.md file.Use the requirements skill to turn these rough notes into a requirements document: I need a CLI tool that parses markdown and generates HTML
High-intent search queries and answers about installing and using this skill.
To turn rough notes into a structured requirements document, you provide your initial scribbles to the tool. It acts as a technical product manager, outputting a formal REQUIREMENTS.md file with sections for functional requirements, success metrics, and open questions.
A generated REQUIREMENTS.md file includes structured sections for Overview, Problem Statement, Users, Functional Requirements, Non-Functional Requirements, Out of Scope, Success Metrics, Assumptions, and Open Questions to ensure comprehensive feature definition.
Yes, you can define feature requirements for a Scrum team from unstructured text. The tool transforms rough notes into atomic, testable, and unambiguous requirements, ensuring your team has a clear, actionable document before development begins.
To identify gaps in feature definition notes, the tool proactively analyzes your rough input and asks clarifying questions. It ensures all sections of the requirements document are populated by requesting missing information before finalizing the output.
The best way to document success metrics and assumptions for product management is to generate a formal requirements document. The tool automatically structures these elements into dedicated sections, ensuring your feature definition remains testable and unambiguous.
mdmagnuson-creatorGenerate a structured PRD saved to docs/drafts/prd-[feature-name].md from user input and project context.
aibangjuxinPrioritize product backlogs using RICE and MoSCoW frameworks.
danzam98Generate a structured Product Requirements Document with goals, user stories, and requirements.
Jia-Hong-PengGenerate structured implementation plans from spec.md files using spec-kit workflows.