enrich-us

Analyze incomplete ticket details and generate implementation-ready markdown user stories.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Andresch2/Workflows --skill enrich-us-andresch2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enrich-us
Source: https://github.com/Andresch2/Workflows/tree/main/ai-specs/skills/enrich-us
Command: npx skills add https://github.com/Andresch2/Workflows --skill enrich-us-andresch2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enrich-us converts incomplete or vaguely specified tickets into user stories that include the technical details needed for engineering execution.

Core Features & Use Cases

  • Story completeness validation: Checks whether the ticket includes full functionality, update targets, required endpoints/URLs, and a clear definition of done.
  • Implementation-ready enhancement: Rewrites the story into a clearer, more specific, concise format aligned with product and technical best practices.
  • Jira-assisted enrichment (optional): When a Jira key/id is provided or Jira is requested, fetches ticket details via Jira MCP and can append enhanced content back to the ticket.

Quick Start

Use enrich-us to analyze and enhance the ticket text you provide, and return an improved markdown version with both the original and enhanced sections.

Frequently Asked Questions about enrich-us

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

FAQPage Schema
How do I turn rough Jira tickets into implementation-ready user stories?

To turn rough tickets into implementation-ready user stories, you analyze incomplete ticket details and rewrite them into a clear markdown format with required technical scope. This process adds required endpoints, fields to update, and a definition of done for engineering execution.

What is user story enrichment for product engineering handoff?

User story enrichment is the process of validating ticket completeness and enhancing vague requirements into specific, concise formats. It ensures the output includes technical scope such as API endpoints, documentation updates, and unit tests for seamless product engineering handoff.

How do I add a definition of done and required endpoints to an incomplete ticket?

You can add a definition of done and required endpoints by applying completeness validation to the ticket text and rewriting the story. This enhancement ensures the final markdown specification includes all necessary technical scope for implementation.

Can I use Jira to automatically fetch and append enhanced ticket details?

Yes, you can fetch and append enhanced ticket details using Jira by providing a Jira key or ID. When Jira is requested, the system retrieves ticket details via Jira MCP and can append the improved implementation-ready content directly back to the original ticket.

What does ticket completeness validation check for in a user story?

Ticket completeness validation checks whether a user story includes full functionality, update targets, required endpoints or URLs, and a clear definition of done. This ensures the rewritten markdown story meets product and technical best practices before engineering handoff.