triage

Decompose large feature requests into dependency-ordered epic specs.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill triage-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/triage
Command: npx skills add https://github.com/curdx/curdx-flow --skill triage-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triage turns a large, vague feature request into a coordinated set of smaller specs with clear dependencies, so Claude Code can execute without losing direction or skipping verification.

Core Features & Use Cases

  • Epic orchestration: Detects whether an epic is active, supports continuing it, and otherwise creates a new epic plan.
  • Dependency-aware spec decomposition: Produces a reviewable epic.md and a dependency-ordered spec list so work can start safely.
  • Coordinator delegation: Assigns exploration, decomposition, and validation tasks to the appropriate subagents instead of implementing directly.
  • Branch + routing discipline: Enforces branch management and routes the goal into the expected workflow topology before writing epic progress.

Quick Start

Run /curdx-flow:triage "my-epic-name" "Build a feature that lets users manage projects with create/edit/delete and browser-verified UI flows."

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose large features into dependency-aware specs without context rot?

Feature decomposition into dependency-aware specs requires breaking down large work into a reviewable epic plan and a dependency-ordered spec list. This prevents completion hallucinations and process mismatch by ensuring work starts safely without overwhelming direct implementation attempts.

When do I need epic decomposition for Claude Code workflow routing?

Epic decomposition is needed for Claude Code when a single prompt risks causing context rot, completion hallucinations, or process mismatch. It detects active epics, supports continuing them, and creates a new epic plan with a dependency-ordered starting spec to ensure safe execution.

How do I start an epic plan and generate a dependency-ordered spec list?

To start an epic plan, run the triage command with an epic name and feature description. It delegates exploration and validation tasks to subagents, enforces branch management, routes the goal into the workflow topology, and produces an epic summary with a dependency-ordered starting spec.

Can I use subagent delegation to coordinate epic orchestration and branch routing?

Subagent delegation coordinates epic orchestration by assigning exploration, decomposition, and validation tasks instead of implementing directly. It enforces branch and routing discipline against the repo’s spec conventions while producing an epic summary and dependency-ordered starting spec for safe execution.

What are the limitations of direct implementation for large vague feature requests?

Direct implementation of large vague feature requests risks context rot, completion hallucinations, and process mismatch. Without epic orchestration and dependency-aware spec decomposition, coordination delegation fails to enforce branch management and routing discipline, leading to lost direction and skipped verification.

Does the triage Skill support continuing active epics and branch state handling?

The triage Skill supports continuing active epics by detecting whether an epic is active and handling branch state. It routes the goal into the expected workflow topology, enforces branch management against repo spec conventions, and snapshots epic progress before producing a dependency-ordered starting spec.