Issue Spec Apply
Developmentissue-spec-applyIssue Spec Apply is an Agent Skill for development published in the higress-group/higress repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Implement PROCESS comments for an issue-spec change and keep PR traceability synchronized.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/higress-group/higress/blob/HEAD/.claude/skills/issue-spec-apply/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-spec-apply, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Issue Spec Apply
Use when the user asks for /issue-spec:apply, issue-spec apply, or implementing PROCESS/TASK scopes from an issue-spec change.
Steps
- Read proposal/design/implement issue context and list typed comments with issue-spec comment list --json.
- Confirm issue-spec auth status --json includes the expected GitHub backend. Local gh-authenticated sessions can use the native gh backend; keep ISSUE_SPEC_TOKEN="$(gh auth token)" only as an older-version or forced-rest compatibility path.
- Create or update PROCESS comments with owner agent, scope, dependencies, write ownership, and status.
- Split non-trivial work into independent worker PROCESS nodes when file/module ownership does not overlap; execute independent workers in parallel when available.
- Add dedicated review PROCESS nodes for non-trivial changes. Review PROCESS nodes should own review scopes such as CLI/API behavior, workflow docs, tests, compatibility, or security-sensitive surfaces.
- Link each PROCESS to its TASK comments with issue-spec link.
- Implement the code changes for one PROCESS scope at a time, or integrate completed worker outputs by dependency order.
- Link every worker and review PROCESS to the PR with issue-spec pr link-process.
- Add PR rationale comments on key changed lines with issue-spec pr rationale, each linked to a SPEC comment.
- Mark PROCESS comments done only after implementation/review work and focused verification evidence exist.
Coordinator DAG Execution
- Build the ready set from PROCESS nodes whose dependencies are done.
- Keep immediate blocking work local when the next step depends on it.
- Spawn or assign independent worker agents only when their write ownership is disjoint.
- Spawn or assign independent review agents only when their review scopes are disjoint.
- Integrate completed outputs by dependency order and update PROCESS evidence before marking done.