RunLogosPhase 01 · Requirements
The Requirements Skill guides a structured conversation to produce requirements.md — a single source of truth for everything the software must do, who it serves, and what success looks like.
What it produces
logos/resources/prd/1-product-requirements/requirements.md containing:
- Personas — who uses the product and why
- Pain points — what problems they face today
- Scenario IDs — S01, S02, S03 … each representing one user journey
- Acceptance criteria — one or more verifiable conditions per scenario
How to run it
- Open RunLogos and click Phase 1 → Requirements in the left panel.
- Answer the structured prompts:
- What do you want to build?
- Who are the users?
- What are the main scenarios?
- What are the acceptance criteria?
- When the dialogue ends, RunLogos writes
requirements.md.
Tips
- Be specific about personas. "Admin" is not a persona. "A solo SaaS founder managing their own subscription billing" is.
- Each scenario should be one coherent user journey, not a feature list.
- Acceptance criteria should be observable: "User can log in with email + password and is redirected to the dashboard."
Output format
## Personas
- **Alex** — solo SaaS founder, manages billing manually via spreadsheet, …
## Scenarios
### S01 — User Registration
A new user signs up with email and password.
#### Acceptance Criteria
- AC-S01-1: User receives a confirmation email within 30 seconds.
- AC-S01-2: Unconfirmed accounts cannot access protected routes.