Reviews drafted task specs and routes them to agent-ready, needs-info, or wontfix outcomes.
npx skills add https://github.com/AceCodePt/dotfiles --skill triage-acecodept
Please help me install this Agent Skill. Skill: triage Source: https://github.com/AceCodePt/dotfiles/tree/main/.config/opencode/flows/triage Command: npx skills add https://github.com/AceCodePt/dotfiles --skill triage-acecodept
tasks/ via orch task list and flags broken dependency edges with orch doctor. - Redundancy and Rejection Checks: Searches the codebase for existing implementations and reads .out-of-scope/ records to surface prior rejections before recommending a decision. - Structured Outcomes: Commits agent-ready specs with correct hitl settings, sends needs-info specs back with specific questions, or records rejected enhancements in .out-of-scope/<concept>.md. - Use Case: A maintainer runs /triage on a new fix-auth spec; the skill reproduces the reported bug, checks for duplicate past rejections, grills the requester for missing detail, and commits the spec as agent-ready. ## Quick Start Ask the assistant to review the draft task queue and recommend whether each spec is agent-ready, needs more information, or out of scope.High-intent search queries and answers about installing and using this skill.
Run the triage flow over uncommitted specs in the tasks/ directory. Each spec is reviewed for completeness, verified against the codebase, and routed to agent-ready, needs-info, or wontfix with a recorded rationale.
Rejected enhancements are recorded as concept files in a .out-of-scope/ directory with the reasoning and prior requests. New requests are matched by concept similarity, and prior decisions are surfaced to the maintainer before re-triaging.
A spec is agent-ready when it follows the task template with a runnable verification, describes behavior rather than procedure, avoids file paths, and has the hitl flag set correctly for human-picked or scheduler-eligible work.
A spec goes back as needs-info when the claim cannot be reproduced from its steps or when evidence or a decision is missing. The requester receives the specific gaps, and the spec stays uncommitted until answered.
No. Slices produced by orch task draft from a grilling session are already agent-ready and should not be triaged. Triage only covers work the maintainer did not create, such as raw bug reports and feature requests.
NeoLabHQCreates draft task files in .specs/tasks/draft/ with typed naming and preserved user intent.
EmmittJTrack team tasks as Markdown files in open, in_progress, and closed directories.
amazingloft999-droidInterrogate product plans against the domain model and update CONTEXT.md and ADRs.
whimzyLiveConvert plans and PRDs into actionable issues in project issue trackers.