gaia-validate-story

To validate a story file in isolation, provide a story key to invoke a forked validator context. This checks the story against canonical artifacts, maps findings to PASSED, FAILED, or UNVERIFIED, and records the outcome via review-gate.sh to prevent unverified stories from advancing.

A Review Gate is a traceable record of a story's validation outcome. The skill records canonical verdicts—PASSED, FAILED, or UNVERIFIED—into the story's Review Gate using review-gate.sh, ensuring unverified or incorrect stories do not advance.

Run the skill with a specific story key to trigger automated QA checks. It locates the related story file under docs/implementation-artifacts/{story_key}-*.md and uses a forked Val subagent to validate it against ground truth artifacts.

To run the isolated story validator, the Val subagent must be available in your environment. Additionally, the target story file must exist under the docs/implementation-artifacts/{story_key}-*.md path for the validation to succeed.

Story validation returns an UNVERIFIED status when the forked Val subagent cannot conclusively map the story findings to a clear pass or fail state against canonical artifacts. It may also occur if the required subagent is unavailable or the story file is missing.

Yes, the gaia-validate-story skill prevents contamination of the editor session by invoking the Val subagent in a forked context. This isolation ensures the validation logic runs independently without affecting the current editor environment.