Convert external ticket content into a structured APED story artefact.
npx skills add https://github.com/yabafre/aped-claude --skill aped-from-ticket
Please help me install this Agent Skill. Skill: aped-from-ticket Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-from-ticket Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-from-ticket
This Skill eliminates the manual, error-prone work of translating an external ticket (Linear/Jira/GitHub/GitLab/ClickUp) into an APED-conformant story, including placement decisions, acceptance criteria drafting, and safe handoff.
Run aped-from-ticket with your ticket ID or URL so the Skill can draft a ready-for-dev story and register it in state.yaml.
High-intent search queries and answers about installing and using this skill.
Ticket intake fetches external ticket details and converts them into a structured story artefact with acceptance criteria, correct placement, and state registration. It extracts titles, descriptions, labels, and comments to draft a ready-for-dev story.
Yes, ticket intake supports GitHub issues and GitLab issues alongside Linear, Jira, and ClickUp. It fetches the ticket content and uses it as the source of truth to draft an APED-conformant story artefact for your project.
Ticket intake prevents duplicate intake by checking configured ticket systems against existing state. It avoids re-ingesting tickets already present in state.yaml, ensuring each external ticket maps to a single story without duplication.
Automated ticket intake fetches external ticket content, determines APED placement through epic bucket matching or interactive selection, and writes the story artefact to the correct location while updating state.yaml with optional comment-back to the source ticket.
Yes, provider-specific authentication and tooling checks are required. Ticket intake requires ticket_system to not be none and performs strict argument parsing by ticket system to validate access before fetching content and writing the story.
User validation gates the story writing and state.yaml update to ensure safe handoff. Ticket intake fetches content, drafts the story, and requires explicit validation before writing the artefact and registering it, preventing automatic development execution.
elijahmurrayConfigure GitHub Issues, Linear, Jira, or GitLab for issue tracking.
yabafreRender an APED pipeline and parallel sprint status dashboard from state.yaml.
yabafreDecompose PRDs into user-value epics with exact FR coverage validation.
yabafreOrchestrate parallel story dispatch into per-story worktrees within an APED project.
