analyze

Detects contradictions, coverage gaps, and scope drift across plan, spec, and code.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/sicambria/talkteach-asr --skill analyze-sicambria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/sicambria/talkteach-asr/tree/main/.claude/skills/analyze
Command: npx skills add https://github.com/sicambria/talkteach-asr --skill analyze-sicambria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans drift from the code they were written against and from the specs they claim to satisfy, and approving an inconsistent plan ships the wrong thing. This Skill performs a read-only cross-artifact consistency check before human approval, surfacing every contradiction, coverage gap, and stale citation so reviewers approve against evidence instead of assumptions. ## Core Features & Use Cases - Consistency Matrix: Checks plan-to-intent coverage (gaps and scope drift), plan-to-code grounding (stale path:line citations and missing symbols), plan-internal contradictions, and intent-to-code overlap (already-done work). - Structured Findings Report: Writes a Markdown report classifying each finding by type, location, severity (blocker or warning), and a one-line impact statement, which the /next phase gate requires before advancing to approval. - Use Case: Before approving an implementation plan in a gated workflow, run the consistency check to discover that step 3 cites a file that no longer exists and that an acceptance criterion has no corresponding plan step, then route the plan back for revision instead of approving it. ## Quick Start Run a consistency check on the current plan against its spec and the working tree, and write the findings report so the phase gate can advance to approval.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I check a plan for consistency with code before approval?▼

Run the analyze skill, which reads the plan, the spec it claims to satisfy, and the current tree together. It resolves every path:line citation, walks a consistency matrix, and writes a findings report classifying issues as blockers or warnings.

What kinds of problems does a cross-artifact consistency check find?▼

It finds coverage gaps (acceptance criteria with no plan step), scope drift (plan steps with no backing criterion), grounding failures (stale file or symbol citations), internal contradictions, and work the code already does.

Does the analyze skill modify code or fix the issues it finds?▼

No, it is strictly read-only and non-destructive. Findings route back to the plan for revision or to execution as explicit tasks; the skill never edits anything itself.

When should I run a plan consistency check in a gated workflow?▼

Run it inside the /next workflow at phase 3, which is mandatory before human approval, or standalone whenever a plan has drifted from the code or a spec changed under an in-flight plan.

What happens if the consistency report contains blocker findings?▼

Blocker findings mean the plan should not be approved. The correct outcome is to loop back to the plan phase and revise, since the /next gate will not advance into approval without a clean report on disk.