issue-spec-workflow

Coordinates issue-driven planning, implementation, review, and PR handoff via issue-spec CLI.

9.3k|1.3k|Updated Oct 27, 2022
One-click install
npx skills add https://github.com/alibaba/higress --skill issue-spec-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-spec-workflow
Source: https://github.com/alibaba/higress/tree/main/.agents/skills/issue-spec-workflow
Command: npx skills add https://github.com/alibaba/higress --skill issue-spec-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a strict coordinator protocol for turning a bounded issue into a reviewed pull request, enforcing typed planning artifacts, independent code review loops, and an exact-head human review handoff without skipping or reordering steps.

Core Features & Use Cases

  • Structured Planning Artifacts: Creates and transitions typed Proposal, Design, Implement, TASK, PROCESS, and QUESTION artifacts with deterministic ID allocation per issue.
  • Independent Review Loop: Dispatches a read-only reviewer against the exact base and head, routing P0/P1 findings back to the owning writer until zero remain.
  • Human Review Handoff: Pushes the exact head, creates the provider-native PR/MR, publishes rationale comments, and stops before approval or merge.
  • Use Case: A maintainer on the higress repository selects an issue, lets the coordinator plan and delegate implementation to a worker, runs the automated review-repair loop, and receives a PR link with test results and rationale for final human merge decision.

Quick Start

Use the issue-spec workflow to plan and implement the change for issue 42 in higress-group/higress and hand off the resulting PR for my review.

Frequently Asked Questions about issue-spec-workflow

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

FAQPage Schema
How do I plan and implement a GitHub issue with issue-spec?

Run issue-spec auth status and workflow validate, then default to the --issue path for a bounded change with one writer. Add --proposal, --design, or --implement only when product, design, or coordination risk requires them.

When should I create a PROCESS artifact in issue-spec?

Create PROCESS only for concrete coordination needs such as concurrent code writers, isolation of pre-existing work, enforced path ownership, restartable cross-session handoff, or dependency-ordered integration. File count or using a subagent alone never justifies it.

Does issue-spec-workflow merge pull requests automatically?

No. The workflow stops before approval or merge and hands off the exact head, PR link, test results, and risks to the human. The human reviews provider-native CI and approvals and decides whether to merge.

How are typed artifact IDs like QUESTION-1001 allocated?

New typed IDs use the format TYPE-issue plus a three-digit sequence, so Issue 1 starts at QUESTION-1001 and Issue 44 at QUESTION-44001. Sequences 001-999 are allocated only within the target issue after reading its existing typed comments.

What happens when the independent reviewer finds P0 or P1 issues?

Each P0/P1 finding is routed unchanged to the writer owning the affected code, who repairs it, runs focused tests, and returns a new commit. The same reviewer rechecks the pushed head until zero P0/P1 findings remain.