- Home
- Skills
- Business & Operations
- Business Analyst
Works with the AI tools you already use
Business Analyst
Converts product visions into rigorous, stack-agnostic requirements and prioritized P0 user stories.
$10
Business Analyst
Example session with this skill installed
Turn the vision in ./brief.txt into requirements for a 'TaskFlow' mobile app. The slice goal is to allow users to create and complete a task locally. Hosting is undecided.
- Read your context and instructions
- Compiled the business analyst
- Generated the document
I have analyzed the vision for TaskFlow and generated the requirements contract. I identified two architecture-blocking questions regarding data persistence that must be resolved before the architect can proceed.
docs/requirements.md
Product Name: TaskFlow
Slice Goal: Allow users to create and complete a task locally.
Has UI: Yes
Hosting: Undecided
Status: BLOCKED
Executive Summary
TaskFlow is a focused productivity tool for individual task management. This initial slice covers the core lifecycle of a task—creation and completion—residing entirely on the user's local device.
Personas
Alex (The Freelancer): Needs to quickly offload tasks to clear mental space. Goal: zero-friction entry. Pain: losing focus due to complex menus.
Stories
- P0: As Alex, I want to record a task title so that I don't forget it.
- P0: As Alex, I want to mark a task as done so that it is removed from my active view.
- P1: As Alex, I want to edit a task title to correct typos.
Functional Requirements
- FR-001: The system shall save a task string of up to 256 characters.
- FR-002: The system shall toggle the 'completed' state of any existing task.
- FR-003: Task retrieval from local storage must occur in under 200ms.
Acceptance Criteria
- AC-P0-01: Given a blank input, when the user types "Buy milk" and hits save, Then the list displays "Buy milk".
AC-P0-02: Given an active task, when the user clicks the checkbox, Then the task style changes to strikethrough and it moves to 'Done'.
Out of Scope
- Cloud synchronization.
- User accounts and authentication.
- Categorization or tagging.
Open Questions
| Question | Why it matters | Blocking? |
|---|---|---|
| Where is local data stored? | Determines if we need a local DB vs file system. | YES |
| Should data persist after app close? | Impacts durability requirements. | YES |
Residual
Implemented: no
Stack: not chosen
Next steps
- Resolve the blocking questions regarding local data persistence.
- Provide the updated brief to the Business Analyst.
- Call the software-architect skill once status is 'ready'.
business-analyst.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Vague product visions and fuzzy scope lead to architectural bloat and developer frustration. When requirements lack testable boundaries, teams waste time building features that are not mission-critical or are technically undefined.
What it does
- Interrogates product visions to extract testable claims and identify ambiguous language.
- Defines targeted user personas and maps them to prioritized user stories (P0 to P2).
- Generates functional and non-functional requirements with strict, measurable criteria.
- Identifies architecture-blocking open questions and explicitly defines out-of-scope boundaries.
- Produces a standardized
requirements.mdcontract file to gate downstream development.
Why this beats prompting it yourself
Generic prompts often hallucinate technical stacks or agree with fuzzy logic to appear helpful. This skill enforces a rigorous interrogation phase, refuses to "solutionize" with specific frameworks, and intentionally halts the workflow if critical architecture-blocking information is missing.
Use cases
- Transforming raw stakeholder notes into a developer-ready requirements document.
- Triaging a massive feature list into a lean P0 slice for an initial build.
- Auditing a product brief for hidden technical risks and unstated assumptions.
- Creating a source-of-truth contract before initiating UI design or system architecture.
Known limitations
Does not provide UI wireframes, architectural diagrams, or technology recommendations. Requires a pre-defined vision and slice goal to function.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 1 day ago
- Passed all security checks, Safe to install