Validates that a Product Requirements Document (PRD) contains all required sections for automated story generation.
Validates PRD structure and completeness for automated story generation pipelines.
/plugin marketplace add theinfinityguides/software-assembly-line/plugin install software-assembly-line@software-assembly-lineValidates that a Product Requirements Document (PRD) contains all required sections for automated story generation.
Use this agent as the first step in the planning pipeline, before any story generation or dependency analysis. Run this agent:
## Overview
Brief description of the feature/project.
## Problem Statement
What problem does this solve? Why now?
## Entities
### New Entities
- **EntityName**: Description
- field1: type
- field2: type
### Modified Entities
- **ExistingEntity**: What changes
- newField: type
- modifiedField: old -> new
## User Flows
### Flow Name
1. User does X
2. System responds with Y
3. User sees Z
**Triggers**: What initiates this flow
**Outcomes**: What state changes result
## API Surface
### New Endpoints
- `POST /api/resource` - Create resource
- `GET /api/resource/:id` - Get resource
### Modified Endpoints
- `PUT /api/resource/:id` - Add new field support
## UI Components
### New Components
- **ComponentName**: Purpose, location in app
### Modified Components
- **ExistingComponent**: What changes
## Non-Functional Requirements
- Performance: Response time < 200ms
- Security: Auth required for all endpoints
- Scale: Support 10k concurrent users
## Out of Scope
- Feature X (will be Phase 2)
- Integration with Y (separate project)
## PRD Validation Report
### Status: PASS | FAIL | NEEDS_REVIEW
### Critical Issues (0)
None
### Warnings (2)
1. **Missing Out of Scope section**
- Risk: Scope creep during implementation
- Recommendation: Add "## Out of Scope" section listing excluded features
2. **User Flow "Checkout" missing error cases**
- Location: ## User Flows > Checkout
- Risk: Missing error handling in implementation
- Recommendation: Add "Error Cases" subsection
### Info (1)
1. Consider adding API request/response examples for clarity
### Extracted Metadata
- **Entities Found**: 3 new, 1 modified
- **Flows Found**: 5 user flows
- **API Endpoints**: 4 new, 2 modified
- **UI Components**: 3 new, 2 modified
### Ready for Next Step
- [ ] Fix critical issues before proceeding
- [x] Entity Extractor can run
- [x] Flow Extractor can run
Task(
subagent_type="software-assembly-line:planning:prd-structure-validator",
prompt="Validate the PRD at plans/feat-user-subscriptions.md"
)
PRD Created
↓
[prd-structure-validator] ← YOU ARE HERE
↓
Pass? → [entity-extractor] + [flow-extractor]
↓
Fail? → Return issues to author
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences