MUST be invoked at the START of any session that touches the GitHub Projects board, BEFORE running any gh issue / gh project / gh pr command tied to ticket workflow. Trigger phrases include but are not limited to - 'the backlog', 'the board', 'the kanban', 'this epic', 'this ticket', 'this issue', 'pick up N', 'work on N', 'what's next', 'what should I do next', 'move to Doing/Review/Done', 'create an epic', 'create a sub-issue', 'break this into tickets', 'add to the project', 'prioritize', 'plan this work', 'what's in the backlog', 'review the board'. Also fires when the user pastes a GitHub Projects URL, an issue number prefixed with , or asks about how a ticket fits its epic. If in doubt — invoke. The cost of invoking unnecessarily is near zero; the cost of skipping is silent drift from the team's workflow.
EnglishDEFAULT workflow for any ticket / PR / fix work in a GitHub-Projects repo. Use when the user asks to 'iterate on tickets', 'fix these issues', 'work through the backlog', 'run ticket lifecycle', 'process these tickets', or provides issue numbers / an epic / a board column. ALSO use — in adapted form — for any single ticket, single PR, or fix where the full Phase 1→7 lifecycle (or any meaningful subset of it) applies. The skill is modular: use only the phases that fit. Do not refuse to invoke just because you can't run every phase, can't dispatch subagents, or are in a constrained environment (single thread, sequential, no worktrees). Pick the phases that apply and run them; skip the rest explicitly.
English
AGENT SKILLS ATLASIncludes Managing Project Backlog and Ticket Lifecycle.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Managing Project Backlog
MUST be invoked at the START of any session that touches the GitHub Projects board, BEFORE running any gh issue / gh project / gh pr command tied to ticket workflow. Trigger phrases include but are not limited to - 'the backlog', 'the board', 'the kanban', 'this epic', 'this ticket', 'this issue', 'pick up N', 'work on N', 'what's next', 'what should I do next', 'move to Doing/Review/Done', 'create an epic', 'create a sub-issue', 'break this into tickets', 'add to the project', 'prioritize', 'plan this work', 'what's in the backlog', 'review the board'. Also fires when the user pastes a GitHub Projects URL, an issue number prefixed with , or asks about how a ticket fits its epic. If in doubt — invoke. The cost of invoking unnecessarily is near zero; the cost of skipping is silent drift from the team's workflow.
Ticket Lifecycle
DEFAULT workflow for any ticket / PR / fix work in a GitHub-Projects repo. Use when the user asks to 'iterate on tickets', 'fix these issues', 'work through the backlog', 'run ticket lifecycle', 'process these tickets', or provides issue numbers / an epic / a board column. ALSO use — in adapted form — for any single ticket, single PR, or fix where the full Phase 1→7 lifecycle (or any meaningful subset of it) applies. The skill is modular: use only the phases that fit. Do not refuse to invoke just because you can't run every phase, can't dispatch subagents, or are in a constrained environment (single thread, sequential, no worktrees). Pick the phases that apply and run them; skip the rest explicitly.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Managing Project Backlog skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.