Convert external PRDs into the Specification-Driven Development format.
npx skills add https://github.com/heltondoria/claude-code-sdd-kit --skill prd-import
Please help me install this Agent Skill. Skill: prd-import Source: https://github.com/heltondoria/claude-code-sdd-kit/tree/main/global/skills/prd-import Command: npx skills add https://github.com/heltondoria/claude-code-sdd-kit --skill prd-import
This Skill automates the conversion of existing Product Requirement Documents (PRDs) from any format into the structured Specification-Driven Development (SDD) format, ensuring no information is lost and preparing it for the development pipeline.
/prd-review step.Import the external PRD located at '~/documents/legacy_product_requirements.docx'.
High-intent search queries and answers about installing and using this skill.
To convert an external PRD to SDD format, the skill ingests your document, inventories its content, and maps it to the 12 standard SDD sections. It extracts features with acceptance criteria and preserves all original text in an appendix.
The best way to import legacy product requirement documents is to use an automated conversion tool that analyzes unstructured text, enumerates features, and identifies missing information. This ensures no original content is lost during the format conversion process.
Yes, the PRD conversion process preserves extra sections by moving them into an appendix. It strictly maintains all original content from your external document while mapping the primary information to the standard sections.
You can extract features and acceptance criteria from unstructured requirements by importing the document into an automated conversion tool. The tool identifies and enumerates features (F1, F2, etc.) directly from the text during the mapping process.
Yes, you can identify missing information in your product requirements document during the SDD conversion process. The tool highlights any missing sections in the standard format that require your additional input.
A limitation when mapping external PRDs to 12 standard SDD sections is that missing information will be identified for user input rather than auto-generated. You must manually review and fill these gaps to complete the specification.
YINUO0101Analyze source artifacts and code to generate structured markdown product requirement documents.
0xHoneyJarConvert PRD and SDD documents into a sprint plan with deliverables and acceptance criteria.
fum1pleGenerate a test-ready specification document from a feature name and objective.
ucirelloParse markdown files to generate hierarchical section outlines and extract section content.