One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mad-analyze
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/mad-analyze
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill mad-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing features based on misaligned spec, plan, and task artifacts leads to rework, scope creep, and wasted engineering effort. This Skill eliminates that risk by validating cross-artifact consistency before any code is written.

Core Features & Use Cases

  • 6 Cross-Artifact Consistency Checks: Validates requirement coverage, scope drift, terminology alignment, assumption consistency, dependency ordering, and integration surface alignment between spec.md, plan.md, and tasks.md.
  • Strict Mode & Severity Tiers: Blocks implementation on high-severity gaps, flags medium/low issues for review, and generates a detailed analysis report with actionable fix suggestions.
  • Parallel Execution Optimization: Stages a context bundle to enable fast parallel subagent fan-out for large artifact sets, reducing analysis time from ~40 minutes to under 7 minutes for complex features.
  • Use Case: Engineering and product teams using MAD (Model-Agile-Development) workflows can run this Skill between task breakdown and implementation to catch planning gaps early, ensuring all requirements are accounted for before development begins.

Quick Start

Use the mad-analyze skill to validate alignment between your current feature's spec.md, plan.md, and tasks.md files before starting implementation work.

Frequently Asked Questions about mad-analyze

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

FAQPage Schema
How do I validate alignment between spec, plan, and tasks files before coding?

Pre-implementation checks for scope drift detection compare your spec.md and tasks.md to catch planning misalignments. They identify untracked requirements and verify dependency ordering to ensure formal feature delivery artifacts match before development starts.

What is cross-artifact validation in MAD workflows?

Cross-artifact validation in Model-Agile-Development workflows ensures requirement coverage and assumption consistency across planning files. It performs six checks including terminology alignment and integration surface coverage assessment to eliminate rework caused by misaligned specs and tasks.

How do I check requirement coverage and dependency ordering for software features?

Checking requirement coverage and dependency ordering verifies that all spec requirements are mapped to tasks and executed in the correct sequence. This cross-artifact validation catches planning gaps early by flagging high-severity inconsistencies that block implementation.

Can I use parallel subagent execution for spec alignment checks on complex features?

Parallel subagent execution supports spec alignment checks for complex features by staging a context bundle for fast fan-out. This optimization reduces cross-artifact analysis time from roughly 40 minutes to under 7 minutes for large artifact sets.

How do I prevent scope creep from misaligned planning artifacts?

Preventing scope creep from misaligned planning artifacts requires strict failure modes that block implementation upon detecting high-severity gaps. Generating a detailed analysis report with actionable fix suggestions ensures all requirements are accounted for before development begins.

Does strict mode block implementation when finding high-severity planning gaps?

Strict mode blocks implementation when high-severity planning gaps are found during cross-artifact validation. It flags medium and low-severity issues for review while generating a detailed analysis report to guide necessary corrections before coding starts.