challenge

Feasibility scrutiny is performed by dispatching a Challenger subagent to analyze a spec group. It validates environments and dependencies, returning severity-rated findings to identify high-risk areas before proceeding with implementation.

You need to run feasibility checks at pre-implementation, pre-test, pre-review, and pre-orchestration stages. Dispatching validation at these critical workflow gates surfaces blockers and ensures deep scrutiny before proceeding.

You block a workflow orchestrator by dispatching a Challenger subagent that returns Critical severity findings for missing dependencies. The Challenger coordinates with the orchestrator to block progression and provide actionable guidance for the blockers.

The best way to validate end-to-end requirements is to dispatch a dedicated Challenger subagent. It satisfies validation needs by returning severity-rated findings, verifying environments, and coordinating with orchestrator workflows to manage risks.

Yes, the Challenger subagent works with both oneoff-spec and orchestrator workflows. It applies deep feasibility scrutiny across multiple stages to ensure high-risk areas are surfaced regardless of the specific workflow type.

The Challenger subagent returns severity-rated findings categorized as Critical, High, Medium, or Low. These ratings help prioritize risks and determine whether to block or proceed with the current workflow stage.