From accelerator
Resolves configured document-discovery paths for the current project. Used internally by agent definitions that require config-driven directory locations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/accelerator:pathsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!--
These paths are authoritative for all document searches in this project. If a key is missing from the resolved list below (e.g. bang preprocessing was disabled or failed), fall back to the plugin default shown in the legend.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-all-paths.sh
What lives at each path key, with the plugin default if no override is set:
plans — implementation plans for specific work items (default: meta/plans)research_codebase — codebase research outputs on specific work items (default: meta/research/codebase)research_issues — issue / RCA research outputs (default: meta/research/issues)research_design_inventories — design-inventory artifacts, one directory per snapshot (default: meta/research/design-inventories)research_design_gaps — design-gap analysis artifacts (default: meta/research/design-gaps)decisions — architectural decision records for the codebase (default: meta/decisions)prs — PR descriptions for landed changes (default: meta/prs)validations — plan validation reports (default: meta/validations)review_plans — reviews of implementation plans (default: meta/reviews/plans)review_prs — reviews of PR descriptions (default: meta/reviews/prs)review_work — reviews of work items (default: meta/reviews/work)work — work items, often NNNN-title.md (default: meta/work)notes — meeting notes, discussions, ad-hoc context (default: meta/notes)global — cross-repo / org-wide information (default: meta/global)npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorDiscovers project documentation roots and routes questions to the right doc based on query shape. Activates for queries about specs, ADRs, roadmap, bugs, or shared links.
Surfaces the rules, ADRs, specs, and patterns for a code area before changing it. Also recaps project focus when picking up work or loading context for uncommitted changes.
Discovers Logic IDs and file paths from semantic docs/semantic/ for efficient codebase exploration. Use /discover FEATURE for lookups, keyword search, --prime for business index before Glob/Grep/Explore.