Agent skill
prd-to-features
Convert PRD documents into features.json format with BDD test cases. Use this skill when users need to: (1) convert PRD/design documents into testable feature lists, (2) generate BDD test cases for PRD, (3) create features.json files.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/prd-to-features-baqif2-synapse-agent
SKILL.md
PRD to Features.json
Convert PRD documents into priority-ordered {prd_basename}-{number}.json files containing verifiable BDD test cases.
Conversion Workflow
Phase 1: Analyze PRD Completeness
- Read the PRD document
- Run the 6-dimension validation from completeness-checklist.md for each feature section
- List incomplete points and ask the user:
- I'll provide details — User provides specific information
- Use default assumptions — Mark in
expectedfield with(Default assumption: ...)
Phase 2: Split into Verifiable Behaviors
After determining feature granularity, split each PRD section into independently verifiable behaviors:
PRD Section → Multiple features
Each feature → 1-N BDD test cases
Each BDD → Specific steps + Single expected result
Granularity Principle: Each BDD test case should independently verify a specific behavior.
Phase 3: Priority Ordering
Order features from high to low priority (array order represents priority):
- Core Infrastructure — Base components that other features depend on
- Core Routing/Dispatch — Core logic that determines system behavior
- Basic Capability Implementation — Concrete functionality implementation layer
- Tools/Converters — Supporting toolchain
- Discovery/Integration Mechanisms — Extensibility-related features
- User Interface/Experience — User-facing interaction features
Phase 4: Generate JSON
Generate features.json following the spec.md format:
{
"category": "functional",
"prd": "filename.md#section-anchor",
"description": "Feature description",
"bdd": [
{
"title": "Test title",
"description": "Test description",
"steps": ["Step 1", "Step 2"],
"expected": "Expected result"
}
],
"passes": false
}
Phase 5: Check File Size
- Lines ≤ 1000: Output single
{prd_basename}-{number}.json - Lines > 1000: Split by feature module boundaries into
prd-features-01.json,prd-features-02.json
Output Location
Default output to plans/ subdirectory at the same level as the PRD:
prd-directory/
├── 02-architecture.md # PRD file
└── prd-features-01.json # Generated file
Example Dialogue
User: Convert this PRD to features.json
Assistant:
- Read PRD, run completeness check
- List incomplete points (if any)
- Ask user how to handle them
- Confirm granularity and priority
- Generate features.json to
plans/directory
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?