enrich-us

Rewrites backlog items and user stories into implementation-ready specifications with fields, endpoints, and DoD.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill enrich-us-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enrich-us
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/enrich-us
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill enrich-us-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlog items and pasted user stories are often too thin to drive implementation — missing fields, endpoints, files-to-modify, definition of done, and non-functional requirements. This Skill performs a single-shot rewrite that turns a vague ticket into an implementation-ready specification without Socratic back-and-forth. ## Core Features & Use Cases - Dual input modes: Accepts a backlog ID (e.g. SDD-014) resolved via gh issue view, or a pasted multi-line story used as-is. - Structured validation: Checks the story against seven criteria — functionality description, data shapes, endpoints, files-to-modify, DoD, tests, and non-functional requirements — grounded in the project's pattern catalog. - Deterministic output: Always produces ## Original and ## Enhanced sections, ready to paste into specs/<feature-id>/proposal.md or back into the GitHub issue, with optional --write-back issue commenting. - Use Case: Before running /spec fill SDD-014, run /enrich-us SDD-014 to expand a two-line GitHub issue into a complete story with endpoints, affected files, and acceptance criteria. ## Quick Start Ask the AI to enrich a backlog item by typing /enrich-us SDD-014 or paste a user story and request an implementation-ready rewrite.

Frequently Asked Questions about enrich-us

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

FAQPage Schema
How do I make a GitHub issue implementation-ready?

Run /enrich-us with the issue ID (e.g. /enrich-us SDD-014). The skill fetches the issue via gh issue view, validates it against seven completeness criteria, and outputs an Enhanced section with fields, endpoints, files-to-modify, DoD, and non-functional requirements.

What is the difference between enrich-us and spec fill?

enrich-us is a single-shot rewrite of a backlog item into an implementation-ready story, with no questions asked. spec fill is a Socratic Q&A process (Q1-Q6) for building a full spec. Enrich first when the input is too thin, then run spec fill.

Can I enrich a pasted user story without a backlog ID?

Yes. Paste multi-line markdown directly and the skill auto-detects pasted-story mode, using the text as-is. Backlog-id mode only triggers when the input matches the ID pattern like SDD-014 or AI-001-ollama-public.

When should I not enrich a user story?

Skip enrichment for trivial changes like typos or mechanical renames, for items already containing files-to-modify, DoD, and acceptance criteria, and for exploratory spikes that do not benefit from upfront specification.

Does enrich-us modify the original GitHub issue body?

No. With --write-back it only appends a comment containing an enriched-date marker via gh issue comment. The issue body stays terse; the enhanced version belongs in specs/<feature-id>/proposal.md once the spec is created.