spec-kitty.analyze

Analyze project artifacts for inconsistencies, duplications, and gaps.

3|Updated Dec 3, 2024

Search Tags:#quality assurance #requirements #traceability #project validation #artifact analysis

Ready to run

npx skills add https://github.com/jonesrussell/godo --skill spec-kitty-analyze-jonesrussell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-kitty.analyze
Source: https://github.com/jonesrussell/godo/tree/main/.agents/skills/spec-kitty.analyze
Command: npx skills add https://github.com/jonesrussell/godo --skill spec-kitty-analyze-jonesrussell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies inconsistencies, duplications, ambiguities, and underspecified items across design artifacts, ensuring alignment before implementation.

Core Features & Use Cases

Automated Artifact Comparison: Analyze spec.md, plan.md, and tasks.md for conflicting or missing information.
Duplication & Ambiguity Detection: Highlight redundant or vague requirements and user stories.
Coverage Analysis: Map requirements to tasks, flag gaps, and verify adherence to project charter principles.
Design Validation: Ensure the design artifacts accurately reflect the principles and constraints defined in the charter.
Use Case: Project managers and developers can run this analysis to validate artifact coherence before development sprints.

Quick Start

Run /spec-kitty.analyze after completing the task dependencies to get a report on artifact consistency.

Frequently Asked Questions about spec-kitty.analyze

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

FAQPage Schema

How do I check project artifacts for inconsistencies and gaps before coding?▼

To check project artifacts for inconsistencies, you can analyze design documents, plans, and task lists to identify conflicting information, duplications, and underspecified items. This ensures aligned and comprehensive specifications before development begins.

What is requirements traceability and how does it validate design documents?▼

Requirements traceability validates design documents by mapping requirements directly to tasks and flagging coverage gaps. This process verifies that all artifacts adhere to charter principles and capture critical requirements accurately.

Can I detect duplicate or ambiguous user stories in spec and plan files?▼

Yes, you can detect duplicate or ambiguous user stories by running an automated artifact comparison across spec.md, plan.md, and tasks.md files. The analysis highlights redundant or vague requirements for project validation.

Do I need to modify my project files to perform artifact analysis?▼

No, artifact analysis requires no modification of your project files. It operates by generating detailed reports on artifact consistency, identifying duplications and gaps without altering the original documents.

When should I run an artifact consistency check for quality assurance?▼

You should run an artifact consistency check after completing your design documents and task lists, but before starting development sprints. This ensures conceptual consistency and validates that all critical requirements are covered.