Gnosis Skill Requirements Writer

The problem

Vague requirements lead to bloated epics and untestable tickets. Most AI writers produce "system-centric" stories or messy Gherkin that developers can't actually use for test automation.

What it does

• Converts raw requirements into INVEST-compliant user stories with a strict human-actor focus.
• Splits epic-sized requests into small, independently shippable stories before writing criteria.
• Generates Gherkin-format (Given/When/Then) acceptance criteria for every story.
• Enforces a "no-internal-jargon" policy to ensure stories reflect actual end-user value.
• Identifies and rejects non-testable or "partial credit" acceptance criteria.

Why this beats prompting it yourself

This skill enforces strict structural rules that basic prompting ignores, such as the non-negotiable human-actor rule and the prohibition of system-centric stories. It prevents "Jira junk" by forcing epics to be split into shippable units rather than just acting as permanent folders.

Use cases

• Converting a high-level business requirement into a set of ready-to-code tickets.
• Refining "system stories" or technical tasks into true user-centric stories.
• Generating functional test cases in Gherkin for QA and automation engineers.
• Auditing an existing backlog against INVEST criteria to find unestimable or oversized work.

Known limitations

This skill focuses on authoring and refinement. It does not define the initial business strategy or manage long-term versioning, which are handled by other skills in the Gnosis suite.