Skip to content
cccskills
FreePublished on GitHub

challenge

Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket
Works withGitHub
See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Challenge

Standalone adversarial spec review. Runs the full challenger analysis on an existing grooming spec and outputs a verdict (APPROVED / NEEDS_REVISION / BLOCKED) with MoSCoW-classified findings. Posting to the GitHub issue is your choice — you are prompted at the end.

Step 1 — Locate files

This skill targets wp-media/wp-rocket. Use $ARGUMENTS as the issue number N. Verify both files exist:

  • Issue file: .TemporaryItems/Issues/wp-rocket/issues/<N>.md
  • Spec file: .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md

If the spec does not exist, tell the user: "No spec found for issue #N. Run /groom <N> first to produce one." Stop here.

If only the issue file is missing, sync it:

bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>

Step 2 — Invoke the challenger agent

Invoke the challenger sub-agent with:

  • Issue number N
  • Issue file path: .TemporaryItems/Issues/wp-rocket/issues/<N>.md
  • Spec file path: .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md
  • plan_version: 1 (or detect from the spec's Plan v<N> header if present)
  • CURRENT_MODEL: "standalone"
  • session_learnings: read Section 13 of AGENTS.md if it exists, else pass empty string
  • Repo: wp-media/wp-rocket

STANDALONE MODE — one difference from the normal pipeline run: Skip the StructuredOutput JSON return. Output the full human-readable verdict (APPROVED / NEEDS_REVISION / BLOCKED) and findings in a section titled ## Challenge Report, using the same format the orchestrator would receive (verdict, MoSCoW-classified findings, alternative suggestions).

Step 3 — Offer to post

After the agent responds, display its ## Challenge Report and ask:

Post this challenge report as a comment on issue #<N>? Reply yes to post, no to finish here.

If yes — post with dedup:

EXISTING_ID=$(gh api repos/wp-media/wp-rocket/issues/<N>/comments \
  --jq '[.[] | select(.body | contains("<!-- ai-pipeline:challenge -->"))] | last | .id // empty')

Update with gh api --method PATCH repos/wp-media/wp-rocket/issues/comments/$EXISTING_ID if found, otherwise post a new comment. Body always starts with <!-- ai-pipeline:challenge -->.

If no — finish. Remind the user: if the verdict is NEEDS_REVISION, update the spec at .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md before running /groom <N> again or starting implementation.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

compliance

Free

Check a change against WordPress.org plugin rules and PHPCS standards.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

docs

Free

Update developer-facing documentation to reflect code changes on the current branch. Runs as an inline skill inside backend-agent and frontend-agent (step 2.5 of the internal sequence) after implementation and before DOD. Receives the explicit list of changed files from the implementation agent. No-op if no public API changes occurred.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

dod

Free

Run the Definition of Done checklist for the current wp-rocket branch and report PASS/WARN/FAIL with evidence. Two modes: layer 1 (self-correction inside backend-agent / frontend-agent — resolves FAILs before handoff) and layer 2 (independent orchestrator gate — fresh perspective after handoff). Pass layer: "1" or layer: "2" when invoking.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

e2e

Free

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

groom

Free

Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

issue-workflow

Free

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.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

See all skills by wp-media

Report a problem with this skill