bf-create-tasks

Convert ticket specs into structured tasks.json drafts for implementation planning.

Updated Apr 4, 2026

Search Tags:#workflow #spec #brownfield #generate #digest #task-list

Ready to run

npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-create-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bf-create-tasks
Source: https://github.com/ricky-yosh/agent-workflows/tree/main/skills/brownfield/bf-create-tasks
Command: npx skills add https://github.com/ricky-yosh/agent-workflows --skill bf-create-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning a ticket spec into a structured tasks.json for implementation planning.

Core Features & Use Cases

Reads existing spec.txt from .aw/brownfield-progress and generates a draft tasks.json with fields category, description, steps, and done.
Writes the draft to .aw/brownfield-progress/tasks.json.draft and triggers digest generation via the /create-digest skill.
Supports iterative reviews and progressive refinement of tasks for end-to-end delivery.

Quick Start

Run the /bf-create-tasks command after you have an existing spec in .aw/brownfield-progress/spec.txt to generate a draft tasks.json.

Frequently Asked Questions about bf-create-tasks

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

FAQPage Schema

How do I convert a spec into structured implementation tasks?▼

To convert a spec into structured implementation tasks, this skill reads your spec.txt and generates a draft tasks.json with fields like category, description, steps, and done for review-ready planning.

When do I need to generate a task list for brownfield workflows?▼

You generate a task list for brownfield workflows when a spec already exists and your team needs a concrete, review-ready task digest to proceed with end-to-end delivery and implementation.

How do I create a tasks.json draft from an existing spec file?▼

To create a tasks.json draft, run the command after placing your existing spec in the brownfield progress directory, which triggers automated digest generation for iterative review.

Does generating a task digest require an existing spec file?▼

Generating a task digest requires an existing spec.txt file located in the brownfield progress directory, as the skill reads this input to produce the structured tasks.json output.

What is the best way to break down a ticket spec for implementation planning?▼

The best way to break down a ticket spec is to automate conversion into a structured tasks.json, enabling iterative reviews and progressive refinement of tasks for delivery.

Why is my task list generation not writing the tasks.json file?▼

Task list generation initially writes a tasks.json.draft file rather than the final tasks.json, requiring iterative reviews and progressive refinement before finalizing the implementation plan.