lisa-epic-triage
A rigid triage protocol to break down complex epics into actionable, well-defined tasks before coding begins.
Install
mkdir -p .claude/skills/lisa-epic-triage-codyswanngt && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18645" && unzip -o skill.zip -d .claude/skills/lisa-epic-triage-codyswanngt && rm skill.zipInstalls to .claude/skills/lisa-epic-triage-codyswanngt
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
9-step epic triage and 5-step implementation workflow. Ensures epics are fully scoped, broken down, and ordered before execution begins.Key capabilities
- →Verify full scope understanding of an epic
- →Break down epics into concrete bugs, tasks, or stories
- →Identify cross-cutting concerns for an epic
- →Determine correct order of execution based on dependencies
- →Define overall test strategy for an epic
How it works
The skill guides through a 9-step triage process to ensure epics are fully understood, broken down, and ordered before implementation begins.
Inputs & outputs
When to use lisa-epic-triage
- →Reviewing project epics
- →Breaking down features into tasks
- →Verifying implementation readiness
- →Defining acceptance criteria
About this skill
Epic Triage
Follow this 9-step triage process before implementing any epic. Do not skip triage.
Triage Steps
- Verify you have all information needed to understand the full scope of this epic (goals, acceptance criteria, impacted systems, design specs, dependencies, etc.). Do not make assumptions. If anything is missing, stop and ask before proceeding.
- Verify the epic is broken down into concrete, well-scoped bugs, tasks, and/or stories that are each fully triaged. If ambiguities exist, stop and resolve them before breaking it down.
- Identify all cross-cutting concerns (auth, performance, security, data migrations, third-party integrations) that need to be addressed across the epic.
- Identify all dependencies between tasks within the epic, or on external epics, teams, or services. Determine the correct order of execution.
- Verify you have access to the tools, environments, and permissions needed to deploy and verify all tasks within this epic (e.g. CI/CD pipelines, deployment targets, logging/monitoring systems, API access, database access). If any are missing or inaccessible, stop and raise them before proceeding.
- Define the overall test strategy for the epic (unit, integration, end-to-end, load testing).
- Define the documentation that will need to be created or updated to cover the full scope of the epic so another developer understands the architecture, design decisions, and implementation.
- Define measurable acceptance criteria that confirm the epic is fully complete.
- Define how you will verify the epic is fully delivered beyond a shadow of a doubt (e.g. deploy to the target environment, walk through all acceptance criteria end-to-end, confirm all child tasks/stories are closed, confirm no regressions).
Implementation
- Use the output of the triage steps above as your guide. Do not skip triage.
- Work through each task and/or story in the order defined during triage, respecting dependencies.
- Apply the Bug Implementation and Task Implementation processes to each child bug or task, respectively, as you work through them.
- Continuously update the epic and its child issues in JIRA as progress is made.
- Do not consider the epic complete until all acceptance criteria are verified in the target environment and all child issues are resolved.
When not to use it
- →When skipping any of the 9 triage steps
- →When making assumptions about epic scope
- →When ambiguities exist in epic breakdown
Limitations
- →Requires verification of all information needed to understand the full scope
- →Requires resolution of ambiguities before breaking down the epic
- →Requires access to tools, environments, and permissions for deployment and verification
How it compares
This skill enforces a structured, multi-step triage process for epics, ensuring all aspects are considered before coding, unlike directly proceeding to implementation.
Compared to similar skills
lisa-epic-triage side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| lisa-epic-triage (this skill) | 0 | 21d | No flags | Intermediate |
| task-master | 22 | 5mo | Review | Intermediate |
| spec-kit-workflow | 11 | 7mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by CodySwannGT
View all by CodySwannGT →You might also like
task-master
sfc-gh-dflippo
AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
agile-product-owner
davila7
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
writing-plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
feature-design-assistant
davila7
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.