Gnosis Skill Business Analyst

The problem

Vague stakeholder notes and raw feature requests often enter the backlog as half-baked solutions. When requirements are confused with implementation tasks, teams build the wrong things or get stuck with untraceable tech debt.

What it does

• Extracts the root cause from raw stakeholder notes using a structured "why" analysis.
• Classifies input into distinct Requirements, User Stories, or Tasks to prevent system-as-actor errors.
• Identifies and structures Non-Functional Requirements (NFRs) like performance, security, and scalability.
• Flags regulatory constraints and translates them into testable, jurisdictional requirements.
• Groups requirements into themes such as Growth, Retention, or Platform Stability to aid prioritisation.

Why this beats prompting it yourself

General LLMs often turn system tasks into fake user stories like "As the database, I want to..." this skill enforces a strict requirements engineering methodology. It ensures every ask is filtered through a root-cause check and correctly categorized before it reaches your backlog.

Use cases

• Converting a messy 30-minute meeting transcript into structured, themed requirements.
• Auditing a list of feature requests to separate engineering tasks from human-centric stories.
• Defining testable performance benchmarks and NFRs for a new service.
• Translating regional regulatory obligations into specific, testable constraints.

Known limitations

This skill focuses on structuring and classification, it does not write final Gherkin acceptance criteria or user stories. Those should be handed off to a specialized requirements writer skill.