spec-kitty.analyze

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.

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.

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.

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.

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.