spec-optimizer

To audit project specifications, you can use a workflow that scans directories like .trellis/spec to surface omissions, redundancy, duplicate definitions, and cross-file conflicts, ensuring consistency and traceability.

The best way to resolve specification conflicts is through a guided workflow that prioritizes findings by severity and prompts you to make decisions one item at a time, ensuring careful cross-file alignment before applying edits.

Yes, this spec audit workflow directly supports scanning .trellis/spec and related documentation directories to identify drift, duplicate definitions, and inconsistencies across your project files.

You can fix specification drift and redundancy by running an audit that detects these issues, then following a staged, one-question-at-a-time conflict resolution process to apply guided edits and recheck for consistency.

Yes, you can enforce scope and severity-based prioritization during a spec review, which systematically guides your edits and rechecks to ensure alignment and traceability across all related project documentation.