Project-documentation router. Use BEFORE any planning, investigation, debugging, or implementation task — whenever the user asks to "plan X", "investigate Y", "figure out why Z", "debug this", "fix this bug", "add a feature to", "explore how X works", "why does", "how does", "onboard onto this code", or otherwise needs to understand existing functionality before acting. Reads `docs/INDEX.md` (auto-maintained by the codelore `document-feature` skill) and pulls only the implementation docs whose `description` or `triggers` match the current task into the agent's working context, so the agent doesn't plan or fix in the dark. If `docs/INDEX.md` is missing in a project that already has `docs/`, suggests running the `migrate-project-docs` skill before continuing. This is NOT for writing docs (that's `document-feature`) and NOT for exploratory critique (that's `exploratory-qa`) — it is for surfacing the right existing docs at the right moment.
Create and maintain implementation documentation that describes how features work, why they were built the way they were, and what to watch out for when modifying them. Use this skill whenever the user asks to "document what was implemented", "write up how this works", "document this feature", "update the docs for this", or any request to produce or update technical documentation about implemented functionality. Also trigger when the user finishes implementing a feature or making significant changes and asks to wrap up — suggest documentation if it hasn't been requested. This skill does NOT produce changelogs, session logs, or decision records. It produces living reference documents that explain the approach, the problem it solves, trade-offs, and what a future developer (human or AI) needs to know to safely modify the functionality.
Exploratory QA agent that critically examines a feature, area of code, or implementation plan to surface non-obvious decisions, unusual implementations or design choices, and architectural choices that deserve discussion. Use when the user asks to "explore this feature", "review this area critically", "QA this plan", "critique this spec", "review this implementation plan", "find non-obvious things", "question this implementation", "QA this module", or any request to examine code OR a plan with a skeptical eye. Also use when the user wants to understand why code is written in a surprising way, when onboarding to unfamiliar code, or when pressure-testing a design document before implementation. This is NOT a linter, style checker, or bug finder. It is a thinking agent that asks "why?"
One-shot bulk migration that prepares a project's existing documentation for the codelore router (`consulting-project-docs`). Use when the user asks to "migrate the docs", "set up codelore docs", "index existing documentation", "add frontmatter to the docs", or when `consulting-project-docs` detects that `docs/INDEX.md` is missing in a project that already has `docs/`. Walks `docs/`, classifies each `.md` file as an implementation doc, a plan/spec, or ambiguous, asks the user about the ambiguous ones, then bulk-adds YAML frontmatter to approved implementation docs and writes `docs/INDEX.md`. Idempotent — re-running on a fully migrated tree is a no-op. Skips silently if there is nothing to migrate. Does NOT touch files under `docs/plans/`, `plans/`, or `specs/`. This is a one-time setup skill per project (with delta migrations for newly added unfrontmattered docs); it is not for ongoing doc authoring — that is `document-feature`.