task-brief-creator

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/.

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.

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.

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.

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.

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.