validating

Verify phase contracts, story maps, and bead graphs before code execution.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanpersie2001/pulse --skill validating-quanpersie2001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validating
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/validating
Command: npx skills add https://github.com/quanpersie2001/pulse --skill validating-quanpersie2001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly execution of unclear or risky development phases by verifying that the phase contract, story map, and bead graph are structurally sound and actionable before any code is written. It enforces artifact completeness, runs targeted spikes for HIGH-risk items, polishes bead graphs, and mandates explicit user approval to proceed.

Core Features & Use Cases

  • Artifact Verification: Checks that required history and phase artifacts exist and that each bead follows the canonical schema with required fields.
  • Structural Plan Checking: Runs an isolated plan-checker across eight rigorous dimensions (contract clarity, story coverage, decision mapping, dependency correctness, file scope isolation, context budget, verification completeness, and exit-state readiness).
  • Risk Spikes and Polishing: Creates and time-boxes spike beads for HIGH-risk items, executes automated graph analytics and dependency fixes, and performs a fresh-eyes bead review before approval.
  • Approval Gate: Produces a structured approval summary and requires explicit user consent; updates durable state only after approval to prevent premature execution.

Quick Start

Run validating on the current feature to verify the phase contract, execute any required HIGH-risk spikes, polish beads, and present the final approval summary for user sign-off.

Frequently Asked Questions about validating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify phase contracts and story maps before writing code?

To verify phase contracts and story maps, run a structural plan-checker across eight dimensions including contract clarity, story coverage, and dependency correctness to ensure actionable execution before coding.

What is a bead graph schema check and when do I need it?

A bead graph schema check validates that each bead follows the canonical schema with required fields. You need this validation during the handoff from planning to execution to ensure artifact completeness and structural soundness.

How do I time-box spike testing for HIGH-risk development components?

To time-box spike testing for HIGH-risk components, create dedicated spike beads with enforced time-boxes, execute automated graph analytics and dependency fixes, and perform a fresh-eyes bead review before approval.

Can I enforce an approval gate before execution using Pulse?

Yes, you can enforce an approval gate in Pulse by producing a structured approval summary and requiring explicit user consent. Durable state updates occur only after approval, preventing premature execution.

What's the best way to prevent risky development phases from executing?

The best way to prevent risky development phases is to verify phase contracts, run structural plan-checker prompts, execute time-boxed spikes for HIGH-risk items, and obtain explicit user approval before coding begins.

Why does my story map coverage fail the plan-checker validation?

Story map coverage fails plan-checker validation when decision mapping, dependency correctness, or file scope isolation dimensions detect gaps. The checker requires explicit artifact presence and reconciles mirror state to pass.