analyze-features

Audit markdown feature specs for template mismatches and missing capabilities.

1|Updated Feb 26, 2026

Search Tags:#automation #template #specification #audit #plan #features #capability

Ready to run

npx skills add https://github.com/aberrantCode/llm_skills --skill analyze-features

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-features
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/project-manager/sub-skills/analyze-features
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill analyze-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often accumulate feature specification documents that drift from the established template, miss required capabilities, or contain unresolved questions, leading to inconsistent development and planning.

Core Features & Use Cases

Template Alignment: Identifies missing sections and metadata in each spec and suggests updates to match the prescribed template.
Capability Quality Checks: Validates CAP‑ID formatting, priority labels, and completeness of capability statements.
Open Question Tracking: Detects unresolved questions and surfaces them for stakeholder clarification.
Logical Gap Detection: Finds inconsistencies, conflicting requirements, and missing plan coverage.
Plan Coverage Verification: Ensures every capability is represented in an associated plan file.

Quick Start

Ask the skill to audit all feature specifications and provide a summary of required updates.

Frequently Asked Questions about analyze-features

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

FAQPage Schema

How do I audit feature specification documents for template mismatches and missing capabilities?▼

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.

What is the best way to track unresolved questions across multiple feature spec files?▼

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.

Can I verify plan coverage for capability statements in a docs/features directory?▼

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.

Does this feature spec audit work with markdown files that use frontmatter metadata?▼

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.

How do I identify logical gaps and conflicting requirements in feature specifications?▼

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.

What limitations exist when auditing feature specs without accompanying plan files?▼

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.