本文へ移動
cccskills
無料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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

docs

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

dod

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

e2e

無料

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

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

groom

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

wp-media/wp-rocket7672026年10月14日 更新

wp-media のスキルをすべて見る

このスキルの問題を報告する