Individual skill
extract-features
Turn PRD.md into FEATURES.md: permanent feature IDs, MoSCoW priorities, acceptance criteria and the PRD requirement each feature comes from.
skills/extract-features/SKILL.md
Source commit b67f4d3e1161dcf10ac6d8d0e31ca22015474de0
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 310
- Repository last updated
- Oct 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-tools Repository topic
- ai-workflow Repository topic
- claude Repository topic
- claude-code Repository topic
- cursor-ai Repository topic
- llm Repository topic
- prd Repository topic
- prompt-engineering Repository topic
- rfc Repository topic
- vibe-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,167 bytesSKILL.mdcore · 4,167 bytesscripts/trace-check.pyruns · 13,572 bytes
Read excerpt
You are an expert product manager and technical lead tasked with extracting and organizing features from the Product Requirements Document (PRD.md, or the PRD provided in the conversation).
Create a comprehensive FEATURES.md file that clearly outlines all features, organized by priority and category. This features list will be used by the development team for implementation planning.
If PRD-REVIEW.md exists, read it too. Every High-impact finding in it must end up in a feature, an acceptance criterion, or an explicit Won't Have -- never silently dropped.
If any critical information is missing or unclear, ask specific questions before proceeding.
Extract and organize the features by:
1. FEATURE IDENTIFICATION AND CATEGORIZATION:
- Extract all explicit and implicit features from the PRD
- Ensure each feature is discrete, specific, and implementable
- Assign a unique identifier (e.g., F1, F2, F3)