business-analyst
Business Analyst guides you through refining requirements into structured user stories using the As-a/I-want/So-that format while ensuring INVEST compliance. It extracts and references existing business rules from your project docs, investigates domain entities, and generates acceptance criteria in BDD (GIVEN/WHEN/THEN) format to close gaps and improve testability.
Business Analyst helps you write INVEST-compliant user stories with BDD acceptance criteria and business rule traceability.
AI-generated summary based on this skill's SKILL.md
Install
duc01226/EasyPlatform/business-analyst · repository language: C#
git clone https://github.com/duc01226/EasyPlatform
cp -r EasyPlatform/.agents/skills/business-analyst ~/.claude/skills/business-analystnpx skillfed install duc01226/EasyPlatform/business-analystFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write user stories for project management?
Business Analyst helps you structure user stories in the As-a/I-want/So-that format, ensuring they meet INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). Start by identifying the user role, their goal, and the business value. Business Analyst then refines vague requirements into actionable backlog items and validates them against your project context.
How to create acceptance criteria in BDD format?
Business Analyst generates acceptance criteria using GIVEN/WHEN/THEN scenarios that align with Behavior-Driven Development practices. For each user story, Business Analyst defines the preconditions (GIVEN), the user action (WHEN), and the expected outcome (THEN). This format makes criteria testable and ensures shared understanding between stakeholders and developers.
What is the business analyst requirements gathering process?
Business Analyst guides you through extracting and referencing existing business rules from your feature documentation, mapping domain entities to validate stories, and refining vague requirements into clear, structured items. The skill investigates project context, identifies gaps, and ensures each requirement is actionable and traceable back to business value.
How do I refine vague requirements into actionable product backlog items?
Business Analyst takes unclear or high-level requirements and breaks them into specific, testable user stories with INVEST-compliant acceptance criteria. It extracts relevant business rules from your docs, maps domain entities, and generates BDD-format scenarios. This transforms ambiguous ideas into backlog items ready for estimation and development.
What should a user story template with INVEST criteria include?
Business Analyst structures user stories with: (1) As-a/I-want/So-that narrative, (2) INVEST compliance checks, (3) BDD acceptance criteria (GIVEN/WHEN/THEN), (4) referenced business rules from your documentation, and (5) domain entity mappings. Each element ensures the story is independent, negotiable, valuable, estimable, small, and testable before entering development.
How does Business Analyst validate user stories against project context?
Business Analyst maps domain entities, cross-references existing business rules from your feature docs, and checks each story for INVEST compliance and testability. It identifies gaps between requirements and project context, ensures acceptance criteria are specific and measurable, and validates that stories align with overall product goals and constraints.
SKILL.md
rendered from the published skill — quoted content, verbatim
> Codex compatibility note:
>
> - Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
> - User-question prompts mean to ask the user directly in Codex.
> - Ignore Claude-specific mode-switch instructions when they appear.
> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
> - Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
> - If a required step/tool cannot
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/business-analyst/SKILL.md