smith-analyze

Validate cross-artifact consistency across spec.md, plan.md, and tasks.md.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-analyze
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-analyze
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation to surface inconsistencies, gaps, and alignment issues before implementation.

Core Features & Use Cases

  • Vault Logging: writes structured event data to the vault session log for traceability during analysis.
  • Constitution-driven validation: detects violations of MUST/SHOULD principles defined in the constitution and flags missing mandated sections.
  • Coverage mapping: links each requirement and user story to one or more tasks, and identifies uncovered items or orphan tasks.
  • Progressive artifact loading: loads minimal context from spec.md, plan.md, and tasks.md to build a semantic model for efficient analysis.
  • Remediation guidance: surfaces concrete remediation recommendations and optional plan adjustments before proceeding to implement.

Quick Start

Run the /smith-tasks to ensure tasks.md exists, then run /smith-analyze to review cross-artifact coherence.

Frequently Asked Questions about smith-analyze

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

FAQPage Schema
How do I check for inconsistencies between spec, plan, and tasks files before implementation?

Cross-artifact consistency analysis identifies inconsistencies, duplications, and gaps across spec.md, plan.md, and tasks.md. It validates functional and non-functional requirements, detects constitution violations, and surfaces remediation recommendations to ensure readiness before implementation.

What is constitution-driven validation for software artifacts?

Constitution-driven validation detects violations of MUST and SHOULD principles defined in the constitution and flags missing mandated sections. It ensures cross-artifact quality audits enforce compliance across spec.md, plan.md, and tasks.md before implementation proceeds.

How do I map requirements to tasks and find uncovered user stories?

Coverage mapping links each requirement and user story to one or more tasks, identifying uncovered items or orphan tasks. It builds a semantic model from progressive artifact loading to detect alignment issues across spec.md, plan.md, and tasks.md.

When should I run cross-artifact quality audits in my development workflow?

Run cross-artifact quality audits after task generation and before proceeding to implementation. This non-destructive analysis surfaces concrete remediation recommendations and optional plan adjustments to resolve alignment issues early.

Can I use this analysis if my tasks.md file does not exist yet?

No, tasks.md must exist before running cross-artifact consistency analysis. You should run task generation first to ensure tasks.md is created, then perform the quality audit to review cross-artifact coherence across spec.md, plan.md, and tasks.md.