Map configured documentation paths to files and directories from .cursor/config.json.
npx skills add https://github.com/softmg/product-tracker --skill docs-softmg
Please help me install this Agent Skill. Skill: docs Source: https://github.com/softmg/product-tracker/tree/main/.cursor/skills/docs Command: npx skills add https://github.com/softmg/product-tracker --skill docs-softmg
Provides a clear, configuration-driven map of where project documentation lives so contributors and agents can reliably find, create, and update plans, reports, issues, and architecture notes without guessing hardcoded paths.
Read .cursor/config.json to resolve the configured documentation root and then open or create the appropriate file under the mapped develop, design, or changelog paths.
High-intent search queries and answers about installing and using this skill.
Project documentation is located by reading path mappings from .cursor/config.json, which resolves the configured documentation root and avoids hardcoding directories so contributors can reliably find and update files.
Standard documentation areas include dedicated directories for plans, reports, issues, features, api, components, architecture, design, and changelog, each serving a specific intended purpose for organizing project files.
To add an API endpoint spec, read .cursor/config.json to resolve the documentation root, then open or create the appropriate file under the mapped api path while following enforced naming conventions.
Yes, planners can locate the mapped develop or reports paths within the configured documentation root to archive completed tasks and update project tracking files without executing code.
Documentation workflow guidance advises when to update files automatically versus manually based on linking docs to code changes, applying naming conventions, and managing structured directory mappings for reports and architecture notes.
openakitaList files and subdirectories with metadata from a specified directory path.
itsjaviValidate .specs planning workflows for structure, completeness, and correctness.
alo-expGenerate developer handoff specs with layout, tokens, component props, states, breakpoints, and accessibility notes from Figma URLs or descriptions.
intelli-verse-xLocate the IntelliVerseX Flutter SDK root and documentation paths.
