gza-task-draft

Guides users through task drafting, risk surfacing, and approval before gza add.

11|1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-task-draft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gza-task-draft
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-task-draft
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-task-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users through a structured, reliable process to create high-quality task prompts for gza add, reducing miscommunication and reruns.

Core Features & Use Cases

  • Clear, step-by-step workflow for task drafting, risk surfacing, and prompt refinement.
  • Encourages explicit acceptance criteria and defined task boundaries before execution.
  • Integrates planning, approval, and execution steps for batch task work.

Quick Start

Draft a precise task prompt and obtain user approval before executing gza tasks.

Frequently Asked Questions about gza-task-draft

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

FAQPage Schema
How do I structure task creation and get prompt approvals before executing batch work?

Task creation is structured by guiding users to clarify scope, surface risks, draft prompts, and obtain formal approvals before execution. This enforces a step-by-step workflow that reduces miscommunication and reruns for multiple coordinated tasks.

What is the best way to draft precise task prompts for gza add?

Drafting precise task prompts for gza add involves a step-by-step process for defining task boundaries and explicit acceptance criteria. This deliberate approach refines prompt design and ensures quality prior to running the execution command.

How do I assess task impact and sequence batch tasks for team coordination?

Assessing task impact and sequencing batch tasks is handled through a structured workflow with dedicated planning steps. Teams coordinate multiple tasks by surfacing risks and defining execution order before running their planned work.

Does this task-drafting workflow support upfront planning for multiple coordinated tasks?

This task-drafting workflow supports upfront planning for multiple coordinated tasks by integrating impact assessment, prompt drafting, and sequencing. It is designed for teams requiring formal approvals and structured planning prior to batch execution.

Why do I need to define acceptance criteria and task boundaries before running gza add?

Defining acceptance criteria and task boundaries before running gza add reduces reruns by ensuring explicit task scope. This deliberate creation process surfaces risks early and guarantees formal approval before execution begins.