enrich-us

Enrich user stories with functional analysis and implementation-ready technical detail from tickets or Jira.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill enrich-us-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: enrich-us
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/ai-specs/skills/enrich-us
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill enrich-us-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? User stories and tickets often arrive with vague descriptions that lack the technical detail developers need to implement them autonomously. This Skill analyzes a ticket, performs a mandatory product strategy analysis, and produces an enhanced, implementation-ready version of the story. ## Core Features & Use Cases - Mandatory Functional Analysis: Applies the product-strategy-analyst agent to assess user value, affected personas, MVP scope fit, business impact, assumptions, and risks before any technical enrichment. - Dual Input Modes: Accepts ticket text pasted directly into the chat, or fetches ticket details from Jira via MCP when a Jira key or reference is provided. - Structured Enrichment Output: Always returns ## Functional Analysis, ## Original, and ## Enhanced sections covering endpoints, fields, files to modify, definition of done, tests, and non-functional requirements. - Optional Jira Write-Back: Appends the enhanced content to the Jira ticket with [original] and [enhanced] sections and moves tickets from To refine to Pending refinement validation. - Use Case: A product manager pastes a rough feature request for a supplier order flow; the Skill returns a functional analysis plus a fully detailed story with API endpoints, data model changes, and acceptance criteria ready for a developer. ## Quick Start Ask the assistant to enrich the pasted ticket text or a given Jira issue key into an implementation-ready user story.

Frequently Asked Questions about enrich-us

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

FAQPage Schema
How do I enrich a user story with technical detail?▼

Paste the ticket text directly into the chat and invoke the enrich-us workflow. It runs a functional analysis first, then returns an enhanced story with endpoints, fields, files to modify, definition of done, tests, and non-functional requirements.

How to refine a Jira ticket using an AI assistant?▼

Provide a Jira issue key or reference such as the ticket in progress, and the Skill fetches details via Jira MCP. It can optionally append the enhanced content to the ticket and move it from To refine to Pending refinement validation.

Does the enrichment workflow require Jira to work?▼

No, Jira is optional. Direct input mode is the default when full ticket text is provided in the chat, and Jira mode only activates when a Jira key or explicit Jira request is given.

What output sections does the enriched user story include?▼

The output always includes three markdown sections: Functional Analysis, Original, and Enhanced. Functional Analysis covers problem and user value, affected personas, MVP scope recommendation, assumptions and risks, and customer-facing versus internal impact.

When is product strategy analysis skipped during ticket enrichment?▼

Functional analysis is mandatory for all new features and major enhancements. It is only skipped for purely technical refactors or chore tasks with no user-facing behavior change, and the reason must be stated explicitly.