develop

Implements GitHub issue acceptance criteria, commits evidence, and pushes a branch for PR review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the implementation of a GitHub issue's acceptance criteria by an AI agent, ensuring every change is committed on a dedicated branch, backed by verifiable evidence, and gated by an independent reviewer before merge. ## Core Features & Use Cases - Issue-driven implementation: Reads the issue body and comments (including rework dispatch notes and prior reviewer findings) and implements only the stated acceptance criteria. - Evidence-gated workflow: Records per-AC evidence with commit SHAs, validates it locally with ztrack check, and pushes the updated body back to the GitHub issue. - Safe escalation path: Stops and posts a structured decision handoff comment instead of guessing when work requires architectural judgment or touches human-required paths. - Use Case: A maintainer comments /agent develop on issue #42; the agent implements the ACs on branch agent/issue-42, records evidence, and the substrate opens an auto-merging PR gated by CI and an independent reviewer. ## Quick Start Dispatch the develop agent on a Ready GitHub issue by setting the issue number in the ZTRACK_ISSUE environment variable so it implements the acceptance criteria and pushes a review branch.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I run the develop agent on a GitHub issue?▼

Set the ZTRACK_ISSUE environment variable to the issue number, typically via a PM dispatch or a maintainer `/agent develop` comment. The agent reads the issue body and comments, implements the acceptance criteria on branch agent/issue-N, and the substrate opens the PR.

How does the develop skill record evidence for acceptance criteria?▼

It edits a temporary copy of the issue body, checks each satisfied AC, sets status to passed, and cites the commit SHA with a proof note. It then validates the file with `ztrack check` and pushes the updated body back to the GitHub issue with `gh issue edit`.

Can the develop agent merge its own pull request?▼

No. The agent holds no merge authority and never opens or merges PRs. The substrate opens the auto-merging PR, and an independent reviewer plus ci and security checks gate the merge via GitHub native auto-merge.

What happens when an issue requires a design decision?▼

The agent makes no code change and escalates by commenting a structured handoff on the issue: the decision needed, options with tradeoffs, rejected approaches, and a recommendation. Escalating cleanly is treated as a successful outcome.

Why does ztrack check fail with issue_missing_assignee?▼

The check reads the `Assignee: <login>` line at the top of the issue body as the owner. If the body is rebuilt from scratch and that line is dropped, validation fails even with perfect evidence, so the body must be edited in place.