Files
antigravity-skills-reference/skills/create-issue-gate/SKILL.md
JX2E bfdc54c252 Add acceptance-driven workflow skills (#277)
* add acceptance-driven workflow skills

* chore: sync acceptance workflow skills metadata

---------

Co-authored-by: sck_0 <samujackson1337@gmail.com>
2026-03-12 12:16:15 +01:00

2.1 KiB

name, description, risk, source, date_added
name description risk source date_added
create-issue-gate Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution. safe community 2026-03-12

Create Issue Gate

Overview

Create GitHub issues as the single tracking entrypoint for tasks, with a hard gate on acceptance criteria.

Core rule: no explicit, testable acceptance criteria from user => issue stays draft and execution is blocked.

Required Fields

Every issue must include these sections:

  • Problem
  • Goal
  • Scope
  • Non-Goals
  • Acceptance Criteria
  • Dependencies/Blockers
  • Status (draft | ready | blocked | done)

Acceptance Criteria Gate

Acceptance criteria are valid only when they are testable and pass/fail checkable.

Examples:

  • valid: "CreateCheckoutLambda-dev returns an openable third-party payment checkout URL"
  • invalid: "fix checkout" / "improve UX" / "make it better"

If criteria are missing or non-testable:

  • still create the issue
  • set Status: draft
  • add Execution Gate: blocked (missing valid acceptance criteria)
  • do not move task to execution

Issue Creation Mode

Default mode is direct GitHub creation using gh issue create.

Use a body template like:

## Problem
<what is broken or missing>

## Goal
<what outcome is expected>

## Scope
- <in scope item>

## Non-Goals
- <out of scope item>

## Acceptance Criteria
- <explicit, testable criterion 1>

## Dependencies/Blockers
- <dependency or none>

## Status
draft|ready|blocked|done

## Execution Gate
allowed|blocked (<reason>)

Status Rules

  • draft: missing/weak acceptance criteria or incomplete task definition
  • ready: acceptance criteria are explicit and testable
  • blocked: external dependency prevents progress
  • done: acceptance criteria verified with evidence

Never mark an issue ready without valid acceptance criteria.

Handoff to Execution

Execution workflows (for example closed-loop-delivery) may start only when:

  • issue status is ready
  • execution gate is allowed

If issue is draft, stop and request user-provided acceptance criteria.