issue-dispatch

Create GitHub issues for DoR-signed-off stories from pipeline state and artefacts.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/heymishy/skills-repo --skill issue-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-dispatch
Source: https://github.com/heymishy/skills-repo/tree/main/.github/skills/issue-dispatch
Command: npx skills add https://github.com/heymishy/skills-repo --skill issue-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating GitHub issues for every DoR-signed-off story slows delivery and risks missing or inconsistent artefacts. This skill automates end-to-end issue creation by reading the pipeline state, relevant artefacts, and governance gates, then producing well-formed issues and recording dispatch metadata.

Core Features & Use Cases

  • Reads .github/pipeline-state.json to identify stories with dorStatus: "signed-off" and no issueUrl.
  • Generates issue bodies based on artefacts and supports two targets: --target github-agent (rich, with full artefact references) and --target vscode (minimal stub, explicit opt-in).
  • Updates pipeline-state.json with issueUrl and dispatchedAt after creation and ensures governance checks are run before merging.

Quick Start

Dispatch all undispatched DoR-signed-off stories by creating GitHub issues from artefacts.

Frequently Asked Questions about issue-dispatch

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

FAQPage Schema
How do I automate GitHub issue creation for DoR-signed stories?

You can automate GitHub issue creation by reading .github/pipeline-state.json for stories with dorStatus "signed-off" and no issueUrl. The skill generates issue bodies from artefacts, creates the GitHub issues, and records issueUrl and dispatchedAt back into pipeline-state.json.

What is a pipeline-state.json file used for in issue dispatch?

A pipeline-state.json file tracks story governance statuses like DoR sign-off and issue dispatch metadata. It identifies undispatched stories, records issueUrl and dispatchedAt after creation, and gates PR creation through governance scripts for pipeline consistency.

Can I generate minimal GitHub issues for vscode instead of full artefact references?

Yes, you can generate minimal GitHub issues by using the vscode target mode. This produces a minimal stub issue instead of the rich artefact references provided by the github-agent target mode, requiring explicit opt-in during the dispatch process.

Does issue dispatch require preflight checks before creating GitHub issues?

Yes, issue dispatch enforces preflight checks before creating GitHub issues from DoR-signed stories. These checks validate pipeline state and artefacts, ensuring governance gates run before merging and preventing inconsistent issue creation.

What artefacts are needed to compose rich GitHub issue bodies for automation?

Composing rich GitHub issue bodies requires reading DOR artefacts and story files. Specifically, it reads artefacts/[feature-slug]/dor/[story-slug]-dor.md and artefacts/[feature-slug]/stories/[story-slug].md to build full issue references for the github-agent target.

Why does my automated issue dispatch fail to create GitHub issues for signed-off stories?

Automated issue dispatch fails to create GitHub issues for signed-off stories when preflight checks detect missing artefacts or invalid pipeline-state.json entries. The skill gates creation on valid dorStatus values and requires undispatched stories without an existing issueUrl to proceed.