analyze-features

Auditing feature specification documents involves parsing markdown spec files to identify missing sections, validate CAP-ID formatting, and detect unresolved questions. The process generates a consolidated audit report highlighting template mismatches and required updates.

Tracking unresolved questions across feature spec files requires pattern matching on markdown frontmatter and sections to detect open items. This surfaces unresolved questions for stakeholder clarification and ensures all capabilities are represented in associated plan files.

Verifying plan coverage involves checking that every capability statement in markdown spec files has corresponding entries in associated plan files. This ensures complete plan coverage and identifies missing capabilities or conflicting requirements within the repository.

Feature spec audits work with markdown files containing frontmatter metadata by performing pattern matching on both frontmatter and document sections. This validates priority labels, checks CAP-ID formatting, and identifies template alignment issues across the specification documents.

Identifying logical gaps in feature specifications requires analyzing markdown spec files for inconsistencies, conflicting requirements, and missing plan coverage. The audit detects template mismatches and generates a consolidated report for user authorization and stakeholder review.

Auditing feature specs without accompanying plan files limits the ability to verify plan coverage and detect missing capabilities. The audit requires a docs/features directory containing both markdown spec files and associated plan files to generate a complete consolidated report.