hj-feature-map

To map natural language feature requests to exact file paths, use a centralized disambiguation reference that translates spoken phrases into specific code targets, URLs, and governance rules, preventing wrong-file navigation during implementation.

Feature disambiguation mapping translates spoken or written feature requests into precise file paths, URLs, and rules within a codebase, serving as a quick reference to ensure consistent feature implementation and prevent navigation errors across teams.

Prevent file navigation errors by consulting a structured feature map before implementing or editing features to ensure you reference the exact files, URLs, and governance rules associated with the requested feature.

You need a feature map during feature discovery, implementation, and review when team members use natural language phrases to describe requests, ensuring everyone references the exact files and rules consistently.

Yes, you can use a feature map during code review to resolve ambiguous component references by translating conversational phrases into exact file targets, ensuring consistent references and reducing miscommunication.

The feature map relies on YAML frontmatter in SKILL.md for its identity and a structured body for mappings, meaning the reference is only as accurate as the documented entries and requires manual updates when codebase structures change.