Review grooming specs and output MoSCoW-classified verdicts.
npx skills add https://github.com/wp-media/imagify-plugin --skill challenge-wp-media
Please help me install this Agent Skill. Skill: challenge Source: https://github.com/wp-media/imagify-plugin/tree/main/.claude/skills/challenge Command: npx skills add https://github.com/wp-media/imagify-plugin --skill challenge-wp-media
Adversarially reviews grooming specs to uncover hidden risks, unvalidated assumptions, and missing dependencies before implementation begins.
Use the challenger to review the specified grooming spec by loading the issue and spec files and running the analysis to produce a verdict.
High-intent search queries and answers about installing and using this skill.
Adversarial review of grooming specs identifies hidden risks, unvalidated assumptions, and missing dependencies before implementation begins. A challenger agent analyzes the issue and spec files to produce a human-readable verdict with MoSCoW-classified findings.
Adversarial review for requirements validation evaluates spec quality before implementation by challenging grooming specs. This process surfaces missing dependencies and unvalidated assumptions, producing a verdict of APPROVED, NEEDS_REVISION, or BLOCKED with classified findings.
Run the standalone challenger agent with a given issue number and related spec files to perform the review. The analysis evaluates spec quality across issue tracking and requirement validation, outputting actionable guidance and a MoSCoW-classified verdict.
Yes, the challenger works as a code-quality gate for pre-implementation reviews and risk assessments in software projects. It analyzes project config and issue-related files to surface actionable guidance, preventing downstream defects by blocking or requiring spec revisions.
The best way to classify findings from grooming spec risk identification is using the MoSCoW method. The challenger agent outputs a human-readable verdict with MoSCoW-classified findings, prioritizing actionable guidance for unvalidated assumptions and missing dependencies.
You should not use an adversarial challenger when a grooming spec lacks defined issue numbers or related project files. The standalone operation requires loading specific issue and spec files to run the analysis and produce a valid verdict with classified findings.
glwrPrepare and publish an Apple app release with versioning and GitHub release creation.
mnfst-aiRequire documented user evidence before staging implementation.
CenredJunDispatch isolated subagents per task with two-stage spec and quality review gates.
tizeeCreate and run standalone Python scripts with inline dependency metadata using uv.
