skills.rest
mrdavidlaing
mrdavidlaingCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

yak-triage

Collect hard-stop time, WIP limits, and must-dos before AI-assisted sprint sessions.

3|3|Updated Feb 13, 2026
Search Tags:#workflow#orchestrator#triage#worklog#task-board#session-planning
One-click install
npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yak-triage
Source: https://github.com/mrdavidlaing/yakthang/tree/main/skills/yak-triage
Command: npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-agent sessions requires upfront constraints to prevent scope creep and unbounded work. Yak-triage enforces hard-stop times, WIP limits, and must-dos before shavers are spawned, so operators stay in control of a session.

Core Features & Use Cases

  • Pre-commitment questions (time window, WIP limit, must-dos) to establish the session boundary.
  • Phase 2: survey the map (read the yak map with yx ls; categorize In flight, Ready, Blocked, Done) to surface actionable work.
  • Phase 3: craft a concise session plan with sizing guidance and priorities before spawning work.
  • Phase 4: commit the session state to a persistent session yak and enforce boundaries during execution.

Quick Start

Start a triage session at the beginning of each work period to set hard-stop, WIP limit, and initial session plan.

Frequently Asked Questions about yak-triage

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

FAQPage Schema
How do I set session scope and prevent scope creep when coordinating multiple AI agents?▼

Session triage enforces scope by collecting hard-stop times, WIP limits, and must-dos before spawning agents, ensuring operators maintain control over multi-agent sprint sessions.

What is the best way to plan work within deterministic boundaries for a task board?▼

Task-board planning uses pre-commitment questions to establish boundaries, then surveys the work map to categorize items as In flight, Ready, Blocked, or Done before crafting a concise session plan.

How do I constrain WIP limits and hard-stop times before starting an orchestrator session?▼

Constraining WIP limits happens during the pre-commitment phase, where the triage process collects time windows and must-dos before any work begins, preventing unbounded execution.

Does session-based triage work without persistent storage for the task board?▼

Session-based triage commits the final session state to a persistent session yak, meaning a storage mechanism is required to enforce boundaries during execution and track progress.

When should I not use a triage workflow for my session planning?▼

Triage workflows are unnecessary for single-agent or ad-hoc tasks without scope risks, as the overhead of pre-commitment phases and WIP enforcement suits coordinated, multi-agent sprint sessions.

Can I use optional resource directories for scripts and references during session planning?▼

Optional resource directories can be used to supply scripts, references, and assets, supporting the orchestrator during the survey and planning phases of the triage workflow.

Related Skills

Explore More Product & Management Skills→
bryan-thompsoncodesbryan-thompsoncodes

workday-sprint

Categorize GitHub Project V2 sprint items by Status for Bryan.

Community
Intermediate
anton-abyzovanton-abyzov
156

smart-reopen-detector

Scan recent completed work and suggest reopening related tasks within WIP limits.

Community
Advanced
script-reposcript-repo

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning via AI swarm coordination.

Community
Advanced
xtrm-devxtrm-dev
4

using-specialists-auto

Orchestrate unattended specialist-agent runs across multi-item priority queues.

Official
Advanced