verify

Grep Task 0 anchors against the codebase and generate a verification report.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/aspelldenny/sos-kit --skill verify-aspelldenny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/aspelldenny/sos-kit/tree/main/skills/attic/verify
Command: npx skills add https://github.com/aspelldenny/sos-kit --skill verify-aspelldenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before coding, this Skill enforces a gate by grepping phiếu assumptions against real code and reporting any mismatches to the Architect.

Core Features & Use Cases

  • Exact grep-based verification of Task 0 anchors against the codebase.
  • Generates a structured verification report highlighting verified, different, and missing anchors.
  • Prevents silent phiếu adaptation by halting progress when issues are found.

Quick Start

Run Task 0 verification for the current phiếu to confirm all anchors before coding.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify codebase assumptions before coding to prevent incorrect implementation?

Verifying codebase assumptions before coding requires greping Task 0 anchors against the actual codebase to validate alignment. This process generates a formal verification report highlighting verified, different, and missing anchors to prevent silent adaptation.

What is a Task 0 anchor table and how does it validate codebase quality?

A Task 0 anchor table is a structured set of assumptions that validates codebase quality by undergoing exact grep verification. It matches expected codebase states against actual code to detect mismatches and halt progress until issues are resolved.

How do I generate a formal verification report for codebase anchors?

Generating a formal verification report for codebase anchors involves running exact grep commands against the current codebase. The report categorizes results into verified, different, and missing anchors to enforce a quality gate before proceeding to Task 1.

Can I use grep commands to halt development when codebase anchors are missing?

Yes, using exact grep commands to validate Task 0 anchors halts development when missing or mismatched anchors are found. This gate prevents silent adaptation by stopping progress to Task 1 until all issues are formally resolved.

Why does my codebase verification gate report mismatches in phiếu assumptions?

A codebase verification gate reports mismatches in phiếu assumptions because the actual codebase has changed or differs from the initial Task 0 anchors. Greping identifies these differences to prevent coding based on outdated or incorrect assumptions.

What do I need to run a Task 0 verification gate against my codebase?

Running a Task 0 verification gate requires exact grep commands, a Task 0 anchor table, and a formal verification report format. These inputs validate phiếu assumptions against the current codebase to ensure alignment before proceeding to Task 1.