orchestrate-epic
Use when you have a multi-ticket epic (many related tickets across repos) and want to work as many as possible in parallel without breaking dependencies, or need to know what is unblocked now — ingest the epic and its child tickets, build the dependency graph from both formal links and free-text "Dependencies" notes, compute a parallel wave schedule, then act as a persistent coordinator that spawns a session per workable ticket and re-verifies what unblocked as tickets finish.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow reads Jira/GitLab epics and child tickets containing free-text "Dependencies" notes and descriptions authored by users and contributors.
- Repository
- AndreJorgeLopes/devflow
- Commit
bd4b70c
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.