qwen_roadmap_auditor_prototype

Auditing a project roadmap involves analyzing markdown files across your codebase to identify incomplete tasks, calculate completion percentages, and verify WSP compliance. This Skill generates actionable reports pinpointing blocking items and missing MCP integrations.

Roadmap compliance auditing detects missing MCP integrations by scanning markdown files across your codebase for specific reference gaps. It identifies outdated skill references and missing connections, generating an actionable report flagging these issues.

Yes, you need access to codebase files and a skills manifest to check for outdated skill references. The audit cross-references your roadmap markdown files against the manifest to identify discrepancies and generate actionable compliance reports.

Yes, you can use external tools like HoloIndex for semantic search during a roadmap audit. This requires access to codebase files and the skills manifest to accurately identify missing integrations and WSP compliance issues.

The best way to verify WSP documentation standards is to audit project roadmap markdown files for compliance. This Skill analyzes your codebase to ensure adherence to WSP standards, generating actionable reports on missing integrations and outdated references.

A limitation of automating roadmap audits is the strict requirement for accessible codebase files and a skills manifest. Without proper access to these inputs and potentially external semantic search tools, the audit cannot accurately identify missing integrations or compliance issues.