OpenParable
Skip to content
← Back to skills

Issue Workflow

Productivity
issue-workflow

Issue Workflow is an Agent Skill for productivity published in the wp-media/wp-rocket repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Work on a GitHub issue by number for wp-media/wp-rocket. Fetches the issue and hands control to the orchestrator skill (running inline in this conversation), which manages grooming, spec review, implementation, lead review, CI, and QA end-to-end.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/wp-media/wp-rocket/blob/HEAD/.claude/skills/issue-workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-workflow, 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 Workflow

Repository: wp-media/wp-rocket

When the user asks to work on an issue by number, such as:

  • /task 123
  • issue 123
  • #123

follow this workflow. The orchestrator runs inline in this conversation — read the user's opening message before kicking it off, since it uses that for escalation calibration (high autonomy / standard / high oversight).

Tooling

Use shell commands as the primary approach. The GitHub MCP (mcp_github_*) may be used if it is connected — but shell is always the safe fallback and is preferred for reliability.

OperationShell (primary)GitHub MCP (if connected)
Issue fetchbash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>mcp_github_github_issue_read
Branch creationbash .claude/skills/issue-workflow/scripts/make-issue-branch.sh—
Staging & committinggit add / git commit—
Pushinggit push -u origin <branch>—
PR creationgh pr createmcp_github_github_create_pull_request
CI monitoringgh pr checks <PR#>mcp_github_github_pull_request_read

Steps

  1. Extract the issue number from the user's message.

  2. Fetch the issue — run bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N> (or use the MCP equivalent). Read the resulting file at .TemporaryItems/Issues/wp-rocket/issues/<N>.md.

  3. Check for parent epics — if Parent Epic (GitHub) or Parent Epics (Task List) has entries, sync each parent with issue-sync.sh <epic-N> and read those files for context.

  4. Check if this is an Epic — if the issue has label epics, Issue Type EPIC, or has sub-issues listed, ask the user: "Work the epic as a whole, or a specific sub-issue?" If a sub-issue is chosen, sync it and proceed with the epic context in mind.

  5. Determine base branch — default is origin/develop unless the user specified otherwise.

  6. Invoke the orchestrator skill inline (do not spawn it as a sub-agent — it runs in this conversation context so it can read the user's intent for escalation calibration):

    Inputs: issue number N, issue file .TemporaryItems/Issues/wp-rocket/issues/<N>.md, base branch

The orchestrator skill manages everything from here: calibration → grooming → spec review → dispatch → implementation → lead review → push & PR → CI → QA → finalize. It spawns the specialist agents (grooming-agent, challenger, backend-agent, frontend-agent, release-agent, lead-reviewer, qa-engineer, ticket-writer) as isolated sub-agents, but the orchestrator itself stays inline so it can surface decisions back to the user naturally.

Monitor progress at .TemporaryItems/Issues/wp-rocket/issue-<N>-workflow-log.html.