draft

Shapes raw GitHub issues into verifiable ztrack work items with acceptance criteria.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill draft-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/.claude/skills/draft
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill draft-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw, untriaged GitHub issues filed by humans are often too vague for an autonomous development agent to pick up. This Skill converts such requests into well-formed, verifiable work items so the develop agent can act on them without ambiguity. ## Core Features & Use Cases - In-place issue shaping: Rewrites the existing GitHub issue body into ztrack form (summary plus 1-3 observable acceptance criteria) without changing its issue number. - Validation and labeling: Runs ztrack check on the drafted body, then marks the issue with the ready label and assigns it for dispatch. - Escalation handling: Labels vague requests needs-info and out-of-authority requests human-required instead of marking them ready. - Use Case: A maintainer files a one-line issue like "fix login timeout". The PM launches this Skill, which rewrites the issue with a source-grounded summary and provable acceptance criteria, validates it, and marks it ready for the develop agent. ## Quick Start Ask the agent to draft the raw GitHub issue referenced in $ZTRACK_ISSUE into a verifiable ready work item.

Frequently Asked Questions about draft

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

FAQPage Schema
How do I turn a vague GitHub issue into an actionable work item?▼

Read the issue with gh issue view, rewrite its body using ztrack issue scaffold with a source-grounded summary and 1-3 provable acceptance criteria, validate it with ztrack check, then edit the issue in place and add the ready label.

How to validate acceptance criteria in a ztrack issue body?▼

Write the drafted body to a temp file outside the repo and run ztrack check on it. The check parses the body and verifies the acceptance criteria are well-formed before the issue is updated on GitHub.

Does drafting create a new GitHub issue?▼

No. Drafting edits the existing issue in place using gh issue edit, preserving its issue number, which serves as its identity and PR cross-reference. A new issue is never opened.

What happens when an issue is too vague to draft?▼

The issue is not marked ready. Instead, the agent comments the specific clarifying questions and applies the needs-info label, or the human-required label if the request touches a semantic stop topic outside the org's authority.

When is the draft skill not needed for an issue?▼

Roadmap-originated issues never need drafting because the planner already writes well-scoped issues with acceptance criteria via tasks:author. Drafting only applies to raw, human-filed requests on an explicit PM request.