fix: correct markdown formatting in product-brief next steps

Fixes #1080
This commit is contained in:
Alex Verkhovsky 2025-12-09 12:45:56 -07:00
parent cf50f4935d
commit ec73e44097

View File

@ -119,7 +119,10 @@ Provide guidance on logical next workflows:
- Success metrics become specific acceptance criteria - Success metrics become specific acceptance criteria
- MVP scope becomes detailed feature specifications - MVP scope becomes detailed feature specifications
**Other Potential Next Steps:** 2. `workflow create-ux-design` - UX research and design 3. `workflow create-architecture` - Technical architecture planning 4. `workflow domain-research` - Deep market or domain research (if needed) **Other Potential Next Steps:**
2. `workflow create-ux-design` - UX research and design (can run parallel with PRD)
3. `workflow domain-research` - Deep market or domain research (if needed)
**Strategic Considerations:** **Strategic Considerations:**
@ -145,7 +148,6 @@ The brief captures everything needed to guide subsequent product development:
- PRD workflow for detailed requirements? - PRD workflow for detailed requirements?
- UX design workflow for user experience planning? - UX design workflow for user experience planning?
- Architecture workflow for technical design?
**Product Brief Complete**" **Product Brief Complete**"