Fetch Jira tickets and convert them into feature briefs.
npx skills add https://github.com/garethrhughes/fragile --skill jira-feature
Please help me install this Agent Skill. Skill: jira-feature Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/jira-feature Command: npx skills add https://github.com/garethrhughes/fragile --skill jira-feature
This Skill removes the manual work of translating a Jira issue into a complete feature brief, so teams can move from ticket to delivery with less friction and fewer missed requirements.
Use the jira-feature skill with a Jira issue key to fetch the ticket, extract its acceptance criteria, and start the feature cycle.
High-intent search queries and answers about installing and using this skill.
To convert a Jira ticket into a feature brief, you parse the issue key or URL to fetch ticket details, extract summary and acceptance criteria, then generate a structured feature document. This removes manual translation work and prepares requirements for downstream development.
Yes, you need a configured Jira MCP server to extract acceptance criteria. The feature intake process checks for this server connection before fetching issue details, ensuring the tool can successfully pull ticket summaries, descriptions, statuses, and explicit or inferred requirements.
Yes, you can use a Jira issue URL for feature intake. The tool parses the URL to fetch ticket data, extracts acceptance criteria, writes a feature document, and hands off directly to the create-feature workflow for design, implementation, review, and PR creation.
The best way to automate Jira feature intake is fetching issue details via MCP, extracting explicit or inferred acceptance criteria, and generating a feature document. This workflow minimizes missed requirements and reduces friction from ticket creation to delivery.
Inferred acceptance criteria extraction works by analyzing the Jira ticket's summary, description, status, and type. It pulls explicit requirements when available and infers missing criteria to ensure the resulting feature brief contains complete end-to-end proposal details for implementation.
A limitation of using Jira tickets for feature development is the potential for incomplete or missing requirements. While the tool extracts and infers acceptance criteria from ticket data, poorly documented issues may yield incomplete feature briefs, requiring manual review before implementation handoff.
albertoiruruetaDraft and file a Jira ticket with project and issue type selection.
rattamnoonPlan UX and UI by conducting a structured discovery interview and producing a design brief.
stoodderVerify feature readiness, create a pull request, and mark the final stage.
coolbeevipVerify code implementations against issue specifications and acceptance criteria.
