business-story-narration

Generate user stories with acceptance criteria from design artifacts.

10|1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/andresdiegolanda/design-first-ai --skill business-story-narration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-story-narration
Source: https://github.com/andresdiegolanda/design-first-ai/tree/main/context/skills/business-story-narration
Command: npx skills add https://github.com/andresdiegolanda/design-first-ai --skill business-story-narration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and AI assistants often conflate implementation details with user-facing intent, producing issue tracker entries that are either over-specified or ambiguous. This Skill separates the business-facing narrative from the engineer-facing contract so stakeholders and implementers share a clear, testable understanding of scope and success.

Core Features & Use Cases

  • Business description generation: Produces a 1-3 sentence, non-technical summary that describes the user's experience and outcome.
  • Acceptance criteria authoring: Generates measurable, independently verifiable criteria written as Given/When/Then or a checklist, covering happy and error paths.
  • Technical notes (optional): Captures implementation-relevant details separately so the business layer remains free of component names, API paths, or framework references.
  • Use case: Convert a set of architecture notes and a Figma screen into a product-ready story for Jira or Linear that product owners can approve and engineers can implement.

Quick Start

Using the /business-story-narration skill, produce a user story statement, a 1-3 sentence business description, and acceptance criteria for [story title] based on the provided story documents and designs.

Frequently Asked Questions about business-story-narration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate user stories from design documents and architecture notes?

To generate user stories from design documents, provide technical context and design artifacts to produce an As a/I want/So that statement, a 1-3 sentence non-technical business description, and measurable acceptance criteria.

How do I write measurable acceptance criteria for Jira or Linear issues?

Measurable acceptance criteria are authored as Given/When/Then statements or checklists, independently verifying scope and success while covering both happy and error paths for issue tracker entries.

How do I separate business descriptions from implementation details in Azure DevOps?

Separate business descriptions from implementation details in Azure DevOps by generating a 1-3 sentence user-facing narrative free of technical jargon, while capturing component names and API paths separately in optional technical notes.

Can I use Figma screens and architecture notes to create product-ready user stories?

Yes, you can convert Figma screens and architecture notes into product-ready user stories by producing a concise narrative and acceptance criteria that product owners can approve and engineers can directly implement.

What is the best way to avoid over-specifying technical details in user stories?

The best way to avoid over-specifying technical details is to separate the business-facing narrative from the engineer-facing contract, ensuring stakeholders and implementers share a clear, testable understanding of scope.