create-issue-gate
Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.
Project & Program ManagementOperations & Supply ChainAI & Automation
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.
When to Use
- You are starting a new implementation task and want a GitHub issue to be the required tracking entrypoint.
- The work must be blocked until the user provides explicit, testable acceptance criteria.
- You need to distinguish between
draft,ready, andblockedwork before execution begins.
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
<Subscribers only
The full skill, its 1 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md |
| Added | 2026-03-12 |
Related skills
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
antigravity-workflows
Use when asked to ship a SaaS MVP, audit application security, build an AI agent, run browser QA, or design a domain model with multiple skills and verified checkpoints.
ask-questions-if-underspecified
Clarify requirements before implementing. Use when serious doubts arise.
