Skill

epic-triage

9-step epic triage and 5-step implementation workflow. Ensures epics are fully scoped, broken down, and ordered before execution begins.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Follow this 9-step triage process before implementing any epic. Do not skip triage.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

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.

Epic Triage

Follow this 9-step triage process before implementing any epic. Do not skip triage.

Triage Steps

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.

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.

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.