business-analyst
Assists with writing requirement documents, specifications, and architecture-level definitions for software features.
Install
mkdir -p .claude/skills/business-analyst-heshansw && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13141" && unzip -o skill.zip -d .claude/skills/business-analyst-heshansw && rm skill.zipInstalls to .claude/skills/business-analyst-heshansw
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user asks for requirements, specification documents, implementation plans, business rules, scope clarification, user stories, acceptance criteria, or architecture-level feature definition in this repository.Key capabilities
- →Write implementation-ready requirement documents
- →Define in-scope and out-of-scope items
- →List functional requirements
- →Include non-functional requirements
- →Describe implementation in practical phases
- →End with clear acceptance criteria
How it works
The skill applies repository-specific rules to write implementation-ready requirement documents, using a numbered format with status and date metadata, describing current/desired states, constraints, risks, and acceptance criteria.
Inputs & outputs
When to use business-analyst
- →Write requirement documents
- →Define acceptance criteria
- →Create user stories
- →Specify technical implementation plans
About this skill
Business Analyst
Use this skill for requirements and specification work in this repository.
Apply these repo-specific rules:
- write implementation-ready requirement documents before coding when the task is primarily about defining behavior
- use
docs/ai/instructions/for formal requirements documents unless the user asks for another location - match the repository's numbered requirements-doc format with status and date metadata
- describe current state, desired state, constraints, risks, and acceptance criteria
- prefer precise requirements over vague advice
- call out edge cases, operational constraints, and failure behavior explicitly
Output expectations
- state the problem being solved
- define in-scope and out-of-scope items
- list functional requirements
- include non-functional requirements where they matter
- describe how to implement the change in practical phases or steps
- end with clear acceptance criteria or definition of done
Repository context
- Claude-specific assets under
.claude/are useful references for existing behavior - Codex-specific assets should live under
.codex/ - parity with Claude should target equivalent workflow outcomes, not Claude-only hook mechanics
- when the task later moves into coding, hand off to
$senior-fullstack-typescript-developer
If the user asks for review after implementation, finish the implementation work first and then use $typescript-pr-reviewer.
When not to use it
- →When the task is not primarily about defining behavior
- →When the user does not need formal requirements documents
- →When the user asks for review after implementation (use `$typescript-pr-reviewer` instead)
Limitations
- →The skill uses `docs/ai/instructions/` for formal requirements documents unless another location is specified.
- →The skill matches the repository's numbered requirements-doc format.
- →The skill prefers precise requirements over vague advice.
How it compares
This skill generates formal, implementation-ready requirement documents tailored to the repository's specific rules and format, ensuring precise definitions and clear acceptance criteria, unlike informal discussions or generic documentation
Compared to similar skills
business-analyst side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| business-analyst (this skill) | 0 | 4mo | No flags | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| linear-ticket | 1 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
manage-issues
momics
Create, update, and close GitHub issues on Momics/iroh-http. USE FOR: filing bugs or feature requests, closing issues with commit links, triaging issues with labels and priority. Ensures consistent structure (Summary, Evidence, Impact, Remediation, Acceptance criteria) and correct label usage. DO NO
tpp
photostructure
Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/.
prd
alfredolopez80
Product Requirements Document generation and management with INVEST-compliant user stories