req-decompose

Parse REQ-XXX sections from requirements.md into structured GitHub issues.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/ubiquitousthey/exo --skill req-decompose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-decompose
Source: https://github.com/ubiquitousthey/exo/tree/main/skills/req-decompose
Command: npx skills add https://github.com/ubiquitousthey/exo --skill req-decompose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual, error-prone work of turning a product-phase requirements document into discrete, implementation-ready GitHub issues so teams can move from planning to execution faster.

Core Features & Use Cases

  • Parses a phase directory's requirements.md for REQ-XXX sections and optional req-meta metadata to extract individual requirements.
  • Expands each requirement into a structured GitHub issue with Background, Goals, Acceptance Criteria, Technical Context, Dependencies, and Open Questions.
  • Supports three actions: scan (preview issues), create (two-pass issue creation with dependency linking and manifest generation), and status (sync issue state and discover downstream artifacts) for traceability across the development pipeline.

Quick Start

Ask the skill to scan the phase directory to preview the GitHub issues that would be created.

Frequently Asked Questions about req-decompose

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

FAQPage Schema
How do I turn a requirements.md document into actionable GitHub issues?

You can preview GitHub issues from requirements.md by running the scan action, which parses REQ-XXX sections and generates expanded issue bodies with goals, acceptance criteria, and technical context without creating them.

How do I generate acceptance criteria and technical context from product requirements?

Generate acceptance criteria and technical context by parsing REQ-XXX sections in requirements.md, which automatically expands each requirement into structured GitHub issue bodies for implementation readiness.

Can I link GitHub issue dependencies automatically when decomposing requirements?

Yes, you can link GitHub issue dependencies automatically by using the create action, which performs two-pass issue creation to establish dependency linking and generates a phase manifest for traceability.

Does req-decompose work with architecture.md files for technical context?

Yes, req-decompose works with optional architecture.md files in phase directories, utilizing the technical context to enrich the generated GitHub issues alongside the parsed requirements.md data.

How do I track requirement traceability across GitHub issues after creation?

Track requirement traceability by using the status action to sync issue states, discover downstream artifacts, and reference the generated phase manifest linking original REQ-XXX requirements to GitHub issues.