2 replies
1 recast
3 reactions
Step 1: Draft a PRD
Get clarity on the product:
- What it does
- Who it’s for
- Key features, goals, & risks
Prompt:
"Write a PRD for my product. The PRD should include a summary of the product's purpose, the target audience, and the problem it aims to solve. Clearly define the goals and prioritize key features and functionality. Describe user flows in detail, along with technical requirements, success metrics to measure performance, and any dependencies, constraints, or risks. Also, include timelines, milestones, and a list of unresolved questions that need to be addressed. Structure the output in a clear and organized format (using bold headers or bullet points) for easy readability, and make sure the plan identifies and addresses any potential gaps or inconsistencies." 1 reply
0 recast
1 reaction
Step 2: Craft user stories
Turn abstract ideas into actionable tasks:
"As a [user], I want to [action] so I can [goal]"
Prompt:
"Using the provided PRD, break down the high-level goals and features into concise user stories using the format: 'As a [user], I want to [action] so that [goal].' Organize the stories under their respective epics, ensuring each story aligns with the primary goal of the epic. Each user story should clearly reflect a feature or requirement, be actionable, and directly address user needs. Cover both primary user flows and edge cases, ensuring the stories are thorough enough to guide development. Keep the stories concise, prioritizable, and aligned with the overall product goals. For example, if the PRD specifies search functionality, a story might read: 'As a user, I want to search by keyword so I can quickly find relevant results.' Optionally, verify that the user stories cover all critical areas and adjust for completeness if needed.” 1 reply
0 recast
0 reaction
1 reply
0 recast
0 reaction
Step 4: Build a design spec
Prioritize clarity in:
- Layouts
- UX copy
- Interaction states
Prompt:
"Using the PRD, user flows, and user stories, write a comprehensive design specification for the product. The spec should include screen definitions, detailed user flows, layout guidelines, components, interaction states (e.g., hover, active, disabled), UX copy, and a style guide (colors, typography, and spacing). Ensure the document is tool-agnostic and suitable for collaboration with AI UI generators. Prioritize clarity, consistency, and usability. Structure the spec to address essential screens and flows first while leaving room for refinement or iteration based on feedback." 1 reply
0 recast
0 reaction
0 reply
0 recast
0 reaction
