SkillsAdd

smithery.ai

business-to-requirements

Transform business ideas, problems, and conversations into structured technical requirements. Use this skill when users want to (1) create a PRD from a vague idea or feature request, (2) derive technical requirements from a business problem, (3) formalize requirements through iterative conversation, or (4) create user stories and acceptance criteria from business needs. Triggers on requests like "help me write requirements", "create a PRD for...", "what should the spec include", or discussions …

First seen Mar 31, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Summary

  • Transform business ideas, problems, and conversations into structured technical requirements.
  • Use this skill when users want to (1) create a PRD from a vague idea or feature request, (2) derive technical requirements from a business problem, (3) formalize requirements through iterative conversation, or (4) create user stories and acceptance criteria from business needs.
  • Triggers on requests like "help me write requirements", "create a PRD for...", "what should the spec include", or discussions about new features/products.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,971 B
  • docs SUMMARY.md 559 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Business to Requirements

Transform vague business ideas into actionable technical specifications through structured elicitation and documentation.

Workflow Decision Tree

Determine the starting point:

  1. Idea → PRD: User has a feature/product idea

- Elicit requirements through questions - Output: Complete PRD document

  1. Problem → Solution Requirements: User describes a business problem

- Understand the problem deeply first - Derive solution requirements - Output: Requirements with rationale

  1. Conversation → Spec: User wants to discuss and refine

- Iterative Q&A to clarify - Build spec incrementally - Output: Formalized specification

Core Process

Step 1: Understand Context

Ask targeted questions to understand:

  • Problem: What problem are we solving? Who has this problem?
  • Users: Who are the primary/secondary users?
  • Success: How will we measure success?
  • Constraints: Timeline, budget, technical limitations?

See [requirementselicitation.md](references/requirementselicitation.md) for comprehensive question templates.

Step 2: Clarify Ambiguity

Surface and resolve:

  • Vague requirements → Specific, measurable criteria
  • Implicit assumptions → Explicit decisions
  • Conflicting needs → Prioritized trade-offs
  • Edge cases → Defined behaviors

Step 3: Structure Requirements

Organize into:

  • User Stories: As a [user], I want [goal], so that [benefit]
  • Functional Requirements: What the system must do (P0/P1/P2)
  • Non-Functional Requirements: Performance, security, scalability
  • Acceptance Criteria: Given/When/Then or checklist format

See [userstories.md](references/userstories.md) for format and examples.

Step 4: Document

Output in requested format:

  • PRD: Full product requirements document
  • User Stories: Story-focused format
  • Technical Spec: Implementation-focused

See [prdguide.md](references/prdguide.md) for PRD structure and examples.

Quick Reference

User Story Format

As a [persona],
I want [goal],
So that [benefit].

Acceptance Criteria:
- Given [context], when [action], then [outcome]

Priority Levels

Level Meaning Guideline
P0 Must Have Launch blocked without this
P1 Should Have Important, target v1.1
P2 Nice to Have Backlog for future

Requirement Quality Checklist

  • Specific (not vague)
  • Measurable (has success criteria)
  • Achievable (technically feasible)
  • Relevant (ties to business goal)
  • Testable (has acceptance criteria)

Example Interaction

User: I want to add notifications to our app

Response approach:

  1. Clarify: What triggers notifications? Push/email/in-app?
  2. Users: Who receives them? Can users configure preferences?
  3. Content: What information in each notification?
  4. Timing: Real-time or batched? Quiet hours?
  5. Edge cases: What if user has notifications disabled?

Then structure findings into user stories with acceptance criteria.

References

  • [PRD Guide](references/prd_guide.md) - PRD structure, writing guidelines, examples
  • [User Stories Guide](references/user_stories.md) - Format, INVEST criteria, domain examples
  • [Requirements Elicitation](references/requirements_elicitation.md) - Discovery questions, clarification patterns, edge cases