task-brief-creator

Convert planning notes into executable briefs with an eight-section template.

18|3|Updated Jan 12, 2026

Search Tags:#automation #validation #workflows #code-review #code-generation #brief #briefset

Ready to run

npx skills add https://github.com/buYoung/skills --skill task-brief-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-brief-creator
Source: https://github.com/buYoung/skills/tree/main/skills/task-brief-creator
Command: npx skills add https://github.com/buYoung/skills --skill task-brief-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams convert planning notes or rough task descriptions into structured, executable work briefs that guide coding agents and reduce back-and-forth.

Core Features & Use Cases

Automatically grounds input into eight standard sections: Work Type, Current State (As-Is), Desired Outcome (To-Be), Scope, Related Files / Entry Points, Side Effect Checkpoints, Acceptance Criteria, Open Questions.
Supports both single-brief and briefset workflows, including an ambiguity gate, codebase review, and a Stage 4 decision table for user-owned decisions.
Validates briefs against the canonical template and provides a deterministic save flow with a structural validator check.

Quick Start

Paste planning notes or rough task descriptions to generate a ready-to-review brief under docs/briefs/.

Frequently Asked Questions about task-brief-creator

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

FAQPage Schema

How do I convert planning notes into executable briefs for coding agents?▼

To convert planning notes into executable briefs, paste your rough task descriptions to automatically generate a structurally sound document grounded in an eight-section template. The skill validates entry points and emits a ready-to-save brief under docs/briefs/.

What sections are required in a structured task brief for code generation?▼

A structured task brief requires eight canonical sections: Work Type, Current State, Desired Outcome, Scope, Related Files, Side Effect Checkpoints, Acceptance Criteria, and Open Questions. This standardization reduces back-and-forth by providing complete context.

How do I generate a briefset for multiple related coding tasks?▼

To generate a briefset for multiple related tasks, input your planning notes to trigger the briefset workflow. The process includes an ambiguity gate and a Stage 4 decision table to handle user-owned decisions across the generated briefs.

Can I validate task briefs against a canonical template before saving?▼

Yes, you can validate task briefs against the canonical template using the built-in structural validator check. The deterministic save flow ensures every brief enforces the eight-section structure and validates entry points before final output.

How does codebase grounding work when creating work briefs?▼

Codebase grounding during work brief creation occurs via a Stage 3 review process that analyzes your existing codebase. This review ensures the generated brief accurately reflects the current architecture and validates the related files and entry points.

What is the best way to handle ambiguous requirements in task briefs?▼

The best way to handle ambiguous requirements in task briefs is through the integrated ambiguity gate and Stage 4 decision table. These mechanisms isolate user-owned decisions, ensuring unresolved questions are explicitly surfaced as Open Questions rather than guessed.