issue-prerequisite

Enforces a hard gate requiring a verified GitHub issue before any work begins.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill issue-prerequisite-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-prerequisite
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/issue-prerequisite
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill issue-prerequisite-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start coding without tracked work items, losing accountability and project visibility. This Skill blocks all work until a GitHub issue exists, is verified, and is properly configured on the project board. ## Core Features & Use Cases - Hard Gate Enforcement: Stops all work until a GitHub issue number is provided, verified via gh issue view, or created through guided user questioning. - Issue Creation Workflow: Gathers title, description, acceptance criteria, type, and priority from the user, then creates the issue with gh issue create. - Project Board Integration: Mandatorily adds the issue to a GitHub Project, sets Status, Type, and Priority fields using cached field IDs, and verifies the setup before proceeding. - Use Case: A developer asks the AI to fix a typo. The Skill halts execution, prompts for or creates a GitHub issue, adds it to the project board with correct fields, and only then allows the fix to proceed. ## Quick Start Before starting any work, check that a GitHub issue exists for this task and create one with proper project board fields if it does not.

Frequently Asked Questions about issue-prerequisite

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

FAQPage Schema
How do I enforce GitHub issues before starting development work?▼

Use a hard gate that verifies an issue exists with `gh issue view` before any work proceeds. If no issue is provided, gather title, description, and acceptance criteria from the user, then create one with `gh issue create`.

How to add a GitHub issue to a project board with gh CLI?▼

Run `gh project item-add` with the project number, owner, and issue URL. Then retrieve the item ID from `gh project item-list` output and use `gh project item-edit` to set Status, Type, and Priority fields.

Does this work with GitHub Projects field automation?▼

Yes, it sets project fields programmatically using cached field and option IDs to minimize API calls. It requires GH_PROJECT_ID, GH_STATUS_FIELD_ID, and related cache variables from a session-start cache step.

What happens if the GitHub issue does not exist?▼

The gate fails and work stops immediately. The Skill reports the error to the user and either asks for a valid issue number or guides creation of a new issue before proceeding.

Is a GitHub issue required for very small changes like typo fixes?▼

Yes, the gate has no exceptions. A minimum viable issue with a title, one-line description, and a single acceptance criterion takes about 30 seconds to create and satisfies the requirement.