Generate the project brief from interview notes. Use when the user has completed a project interview (/pm-interview) and needs the raw notes transformed into a structured project brief.
Generate the project brief from interview notes.
First, read .workflow/interview-notes.md. If it doesn't exist, ask the user to run /pm-interview first or provide project details.
Create docs/project-brief.md using this exact structure:
# Project Brief
## Identity
- **Project:** [Name]
- **Owner:** [Name]
## Goal
[One sentence]
## Who It's For
[Specific audience]
## Success Looks Like
- [ ] [Measurable outcome 1]
- [ ] [Measurable outcome 2]
- [ ] [Measurable outcome 3]
## Constraints
- **Budget:**
- **Timeline:**
- **Tech stack:**
- **Skills:**
- **Other:**
## Delivery & Operations Context
- **How software reaches users:** [from interview — could be app store, OTA, USB flash, CI/CD, manual deploy, etc.]
- **Hardware/infrastructure involved:** [from interview — or "N/A" for pure software]
- **Compliance/regulatory:** [from interview — or "None identified"]
- **Current pain points:** [from interview — what's hard about building/testing/deploying today]
## Key Decisions Made
| Decision | Reasoning |
|----------|-----------|
## Current Status
**Last updated:** [current session or milestone]
**Current phase:** Planning
**Last completed task:** None
**Next task:** Create project roadmap
**Blockers:** None
## Notes for AI
- [Anything that consistently matters across sessions]
Rules:
Also create an empty .workflow/lessons-log.md from the template if it doesn't exist.