mad-traceability

What problem does it solve?

Manually updating multiple feature traceability documents when implementation statuses change is time-consuming and prone to human error, especially for large projects with hundreds of tracked features that require consistent, accurate status records for governance and reporting.

Core Features & Use Cases

• Atomic Dual-File Updates: Automatically synchronizes changes to both feature-traceability.md and _featuremap.md to eliminate documentation drift.
• Status Transition Validation: Prevents invalid backwards status changes and confirms feature IDs exist before making updates.
• Milestone Status Reporting: Generates summary counts of feature statuses for any milestone to track completion progress at a glance. Use case: A development team working within the MAD governance framework can use this skill to instantly update feature statuses after completing implementation or testing, without needing to manually edit multiple markdown files or risk inconsistent records.

Quick Start

Use the mad-traceability skill to mark feature M2-US1-F1 as tested after its full test suite passes successfully.