jira-brief-intake

To convert a Jira epic into a product brief, the Skill reads your Jira issues in read-only mode, maps the epic to an outcome and child issues to user stories, then writes a shippable spec with provenance tracking for downstream decomposition.

Yes, you can generate user stories from a Jira board or sprint scope. The Skill handles sets without a single parent epic by applying JQL-based issue selection and synthesizing child issues into a mapped product brief.

The best way to extract Jira issues into shippable specs without modifying the tracker is using a strict read-only retrieval flow that maps epics to outcomes and child issues to user stories, ensuring provenance tracking for the generated brief.

You do not need a specific Jira issue format for spec intake. The Skill accepts single-epic references, board or sprint scopes, and JQL-based issue sets to perform story mapping and generate a durable product brief.

When downstream decomposition tools are unavailable, Jira brief generation degrades gracefully by providing a fallback or handoff. The Skill still writes the brief shape and preserves provenance for later use.

You use a dedicated spec intake process for Jira epics to turn tracker-based work into a durable product brief. This prevents work from being trapped in issue tracking and provides clear story traces for engineering teams.