create-issue-gate
Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.
What this skill does
# 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`, and `blocked` work 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: ```md ## 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. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.