Create Product Requirements Document
Workflow
Gather requirements - Ask clarifying questions one at a time:
- What problem are we solving?
- What's the proposed solution approach?
- What are the success criteria?
- What team owns this? (ML or Data Engineering)
Determine file location based on team:
- Machine Learning →
companycam/prds/machine_learning/ - Data Engineering →
companycam/prds/data_engineering/
- Machine Learning →
Create the PRD using the template at template.md:
- Fill in sections based on gathered information
- Leave placeholder text for sections that need more detail
- Use lowercase_with_underscores for filename
Create the file using the Write tool, then commit via nb:
nb git add companycam/prds/<team>/<filename>.md nb git commit -m "[nb] Add: companycam/prds/<team>/<filename>.md"Offer Jira integration - Ask if user wants to add to the discovery board:
- If yes, use the
create-ideaskill with the PRD path
- If yes, use the
Guidelines
- Ask clarifying questions one at a time so the user can give complete answers
- Include unfilled template sections for future completion
- Always read the PRD file before creating Jira issue (user may copy-edit)
- PRDs should be concise - cut the fat
- Read an existing PRD in the target folder first to match conventions (Jira link format, section style)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.