bf-triage

Read tasks.json, confirm the first not-done task, and write it to next-task.json.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bf-triage
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/brownfield/bf-triage
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically selects the next brownfield task from progress records and persists the decision, reducing manual triage time.

Core Features & Use Cases

  • Reads .aw/brownfield-progress/tasks.json and identifies the first not-done task.
  • Confirms the selection with the user and records the decision in .aw/brownfield-progress/next-task.json.
  • Integrates with downstream steps in the brownfield workflow to guide the next action.

Quick Start

Use /bf-triage to pick the next not-done task from tasks.json and write it to .aw/brownfield-progress/next-task.json.

Frequently Asked Questions about bf-triage

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

FAQPage Schema
How do I automate selecting the next brownfield task from a JSON progress file?

Automating brownfield task triage involves reading a tasks.json file to find the first not-done task, confirming the selection with the user, and persisting that record to next-task.json for downstream workflow steps.

What is a brownfield workflow and when do I need task triage automation?

Brownfield workflows track in-progress tasks within existing projects. Task triage automation is needed when you want to reduce manual selection effort by automatically identifying incomplete tasks and persisting them for downstream pipeline steps.

How do I persist the selected task record for downstream workflow steps?

You persist the selected task by writing the confirmed task record to a next-task.json file. Downstream workflow steps then read this file to execute the corresponding next action automatically.

Does brownfield task triage require user confirmation before writing the next task?

Yes, brownfield task triage requires user confirmation before proceeding. After reading the task list and identifying the first not-done task, it prompts the user for a decision before writing the resulting task record to disk.

Can I use this task triage workflow if my tasks are not tracked in JSON format?

No, this triage workflow specifically reads task records from a JSON file. You must have your brownfield progress tasks tracked in a tasks.json format for the automation to read, identify, and persist the next task correctly.