How to Use Clearly

Name: Clearly
Author: Clearly

Create professional requirements documents in minutes with AI-guided conversations. Follow this simple step-by-step guide to get started.

Getting Started in 5 Steps

Step 1: Create Your Account

30 seconds

Get started with Clearly by creating your free account. Choose your preferred sign-up method:

Google

GitHub

Step 2: Create a Project

1 minute

Set up your first project from the dashboard:

1Click "New Project" button
2Enter project name and description
3Choose BRD or PRD as starting point

Step 3: Complete the AI Wizard

5-10 minutes

Our AI guides you through creating comprehensive requirements:

Project Goals

Define objectives & success metrics

Target Audience

Describe your users & stakeholders

Key Features

Specify functionality & requirements

Constraints

Budget, timeline, & limitations

Pro Tip: Don't worry about perfection—you can refine and edit everything later!

Step 4: Review & Export

2-5 minutes

Finalize your document and share it with your team:

Edit & Refine

Make adjustments

Export

PDF or Markdown

With stakeholders

Iterate

Update as needed

Mode-Specific Workflows

Step 5a: Prompt Build

Plain Mode

1-2 min

Generate a vibe coding prompt optimized for visual development tools:

1Click "Generate Prompt Build"
2Review and copy the generated prompt
3Paste into your chosen tool

Compatible Tools:

V0.dev

Loveable

Bolt.new

Bubble

Replit

Step 5b: Task List

Technical Mode

1-2 min

Generate detailed implementation tasks for developers:

1Click "Generate Task List"
2Review tasks and download as Markdown
3Import into your development environment

Compatible Tools:

Cursor

Claude Code

VS Code

GitHub Copilot

Your workflow depends on your project mode

The mode is selected in Step 2 when creating your project. Plain Mode is optimized for visual builders and no-code tools, while Technical Mode generates detailed tasks for developers and IDEs.

BRD vs PRD: Which Should You Start With?

Criteria	Start with BRD	Start with PRD
Project Stage	Early stages, concept validation	Business needs already defined
Primary Focus	Business objectives & ROI	Detailed feature specifications
Audience	Executives, stakeholders, investors	Product team, developers, designers
Best For	Securing buy-in & funding	Ready to start development
Time to Complete	5-10 minutes	10-15 minutes

Recommended Approach

For best results, start with a BRD to define business needs, then create a PRD to specify implementation details. This ensures alignment from strategy to execution.

Tips for Creating Great Requirements Documents

Be Specific

The more detail you provide about your requirements, constraints, and goals, the better your final document will be. Avoid vague terms—use concrete examples and measurable criteria.

Think About Users

Always center your requirements around the people who will use your product. What problems are you solving? What value are you delivering? User-focused requirements lead to better products.

Define Success Metrics

Include clear, measurable success criteria so you can objectively evaluate whether your project achieved its goals. KPIs and metrics prevent scope creep and keep teams focused.

Iterate & Update

Requirements documents are living documents that evolve with your project. Update them regularly as your understanding grows and circumstances change. Version control is your friend.