analyze

Audit cross-artifact traceability for a feature slug across planning docs, tasks, and code.

1|Updated Apr 22, 2026

Search Tags:#diff analysis #code review #audit #scope creep #acceptance criteria #traceability #task mapping

Ready to run

npx skills add https://github.com/AbsolutSystems/absolutpowers --skill analyze-absolutsystems

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It catches drift between planning documents, implementation tasks, and changed code by building a traceability audit for a feature slug.

Core Features & Use Cases

AC to Task Coverage: Verifies whether every acceptance criterion is assigned to at least one task.
Task to Code Validation: Checks that completed tasks map to actual changed files in the diff.
Divergence Detection: Flags missing tasks, tasks without code, orphaned code, missing test references, and semantic contradictions.
Use Case: Run it when you need a cross-artifact consistency report before merging a feature branch or handing work to implementation.

Quick Start

Ask the skill to audit the specified feature slug and produce a traceability report with a final consistent or inconsistent verdict.

Frequently Asked Questions about analyze

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

FAQPage Schema

How do I audit acceptance criteria coverage for a feature branch?▼

Auditing acceptance criteria coverage involves mapping each criterion to assigned implementation tasks. This traceability process verifies every requirement has corresponding tasks before code review, ensuring no planned scope is missed.

What is the best way to detect scope creep and orphaned code in a diff?▼

Detecting scope creep requires building an AC-to-task-to-file matrix from your diff. This validation flags orphaned code, missing test references, and semantic contradictions between planned tasks and actual changed files.

How do I validate task to code traceability before merging a feature?▼

Validating task to code traceability requires checking that completed tasks map to actual changed files in the diff. This generates line-level evidence and a final consistency verdict for the merge.

Can I generate a traceability matrix for cross-artifact consistency checks?▼

Yes, you can generate a traceability matrix for cross-artifact consistency checks. It produces an AC-to-task-to-file matrix with divergence classification, yielding a consistent or inconsistent verdict.

Do I need planning docs and task lists to perform a feature diff analysis?▼

Yes, performing a feature diff analysis requires planning docs, task lists, and changed code. The audit cross-references these artifacts to find drift, missing tasks, and unlinked code with line-level evidence.

Why does my traceability audit return an inconsistent verdict?▼

A traceability audit returns an inconsistent verdict when divergence detection finds missing tasks, tasks without code, orphaned code, or missing test references that break acceptance criteria coverage.