triage

Triage untriaged Asana intake pages into Jira tickets, not-needed, or skip.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --skill triage-brandtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/brandtam/rubber-ducky/tree/main/src/skills/triage
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill triage-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the triage workflow for Asana intake pages, helping teams decide whether to push a Jira ticket, mark not-needed, or skip, reducing manual review time.

Core Features & Use Cases

  • Scope-aware triage: filters pages by source, status, and triage state across /triage and /triage --all to surface only untriaged Asana tasks.
  • Decision-driven workflow: for each page, shows the title, current status, and Jira candidacies to help decide push, not-needed, or skip.
  • Push-to-ticket integration: delegates to the /push skill to create Jira tickets when needed.

Quick Start

Triage untriaged Asana pages from the wiki directory by running the triage command in your workspace.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate triage for untriaged Asana intake pages?

Asana triage automation scans wiki/tasks/*.md files to identify untriaged pages, then surfaces a decision workflow to push a Jira ticket, mark not-needed, or skip each item. It filters by source, status, and Jira fields to reduce manual review time.

How does pushing a Jira ticket from Asana tasks work?

Pushing a Jira ticket reads page frontmatter to surface Jira candidates, then delegates to the /push skill to create the ticket. The triage workflow presents this as a decision option alongside marking the task not-needed or skipping it.

Can I filter Asana pages by status and Jira fields during triage?

Yes, triage supports scope-aware filtering across default and full modes. The /triage command surfaces untriaged pages, while /triage --all expands the scope to filter pages by source, status, and triage state using frontmatter data.

What's the best way to review untriaged Asana intake pages in bulk?

The /triage --all command provides bulk triage by filtering all untriaged Asana pages by status and Jira fields. It presents each page's title, current status, and Jira candidacies to help decide push, not-needed, or skip efficiently.

Do I need markdown files in a wiki directory to triage Asana tasks?

Yes, the triage workflow reads frontmatter from wiki/tasks/*.md markdown files to identify source, status, and triage data. These files act as the intake records that the scope-aware filtering and decision workflow process.

When should I skip an Asana page instead of pushing a Jira ticket?

Skip an Asana page when the surfaced Jira candidates do not warrant ticket creation or when the task needs further review. The triage workflow offers skip as a decision option alongside pushing a Jira ticket or marking the page not-needed.