analyze

Extract requirements, tests, and implementation steps into a traceability matrix with gap findings.

12|2|Updated Nov 20, 2025

Search Tags:#consistency #requirements #traceability #analyze #test-cases #spec-drift #tech-decomposition

Ready to run

npx skills add https://github.com/alexandrbasis/claudops --skill analyze-alexandrbasis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/analyze
Command: npx skills add https://github.com/alexandrbasis/claudops --skill analyze-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs cross-artifact consistency checks to ensure the tech decomposition accurately implements the discovered spec, catching drift before coding begins.

Core Features & Use Cases

Read-only analysis of spec artifacts (discovery, JTBD, PRD) and the tech decomposition to surface alignment gaps.
Extract requirements, test cases, and implementation steps, and build a traceability matrix linking REQ → TEST → Step.
Flag gaps and ambiguities with clear [UNCOVERED], [UNTESTED], and related findings for remediation.

Quick Start

Provide the task directory that contains the spec and the tech decomposition artifacts to run a consistency check.

Frequently Asked Questions about analyze

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

FAQPage Schema

How do I check traceability between discovery specs and a tech decomposition plan?▼

Traceability between discovery specs and a tech decomposition plan is checked by extracting requirements, test cases, and implementation steps to build a gap-finding matrix. This cross-artifact analysis tags unresolved items like [UNCOVERED] or [UNTESTED] to enforce alignment before coding begins.

What is spec drift and how do I identify it before development?▼

Spec drift is the misalignment between discovered requirements and the technical implementation plan. You identify it by performing a read-only analysis of spec artifacts and the tech decomposition to surface gaps, flagging ambiguities with clear findings for remediation.

How do I build a traceability matrix linking requirements to test cases and implementation steps?▼

Build a traceability matrix by targeting a task directory to extract requirements, test cases, and implementation steps. The system links REQ → TEST → Step, automatically tagging untested or uncovered items to produce structured output for validation.

Can I run a consistency check on a task directory without modifying the spec artifacts?▼

Yes, this consistency check performs a read-only analysis of spec artifacts and the tech decomposition. It extracts data to surface alignment gaps and produces structured output for review without altering your original files.

What do [UNCOVERED] and [UNTESTED] tags mean in cross-artifact consistency checks?▼

[UNCOVERED] and [UNTESTED] tags flag gaps and ambiguities found during cross-artifact consistency checks. They identify requirements lacking implementation steps or test cases, enforcing traceability by highlighting unresolved items for targeted remediation.

When should I run a requirements traceability analysis in the software development lifecycle?▼

Requirements traceability analysis should run after tech decomposition and before coding begins. It catches drift early by validating that the discovered spec accurately aligns with the planned implementation steps and test cases.