Agent-Skills.md

Agent Skills: Create Issue Gate

Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.

UncategorizedID: sickn33/antigravity-awesome-skills/create-issue-gate

Repository

sickn33/antigravity-awesome-skills
sickn33License: MIT
27,0474,580

Install this agent skill to your local

pnpm dlx add-skill https://github.com/sickn33/antigravity-awesome-skills/tree/HEAD/skills/create-issue-gate

Skill Files

Browse the full folder contents for create-issue-gate.

Download Skill

Loading file tree…

skills/create-issue-gate/SKILL.md

Skill Metadata

Name
create-issue-gate
Description
Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.

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.