rc-enrichment-prompt

# Prompt Enrichment Turn a raw request into an optimized, execution-ready prompt. The output is a **rewritten prompt**, not an implementation. Never start coding or answering the underlying task here. This skill produces, refines, and optionally saves the prompt — nothing else. ## Required input - **raw prompt** (`$ARGUMENTS` when invoked as an argument, otherwise the user's latest request): the original instruction to enrich. If none is discernible, ask the user to paste it instead of inventing one. ## Resolving the `.rc` base directory RC supports monorepos, where more than one `.rc` directory can exist. Before reading or writing any `.rc/...` path, resolve which `.rc` directory this run uses; its parent is the base directory. Treat every `.rc/...` path in this skill as relative to that base. 1. Search the project recursively for `.rc` directories, skipping `node_modules`, `.git`, `vendor`, and any `_archived/` directory. 2. Resolve the base from what you find: - **None found** — use `.rc/` at the project root, creating it on first write. Ordinary single-folder projects behave exactly as before. - **Exactly one found** — use it without asking. - **Two or more found** — a prompt carries no feature slug to disambiguate with, so ask the user which `.rc` to use via the interactive question tool that pauses execution, listing the discovered directories by their path relative to the project root. ## Procedure When this skill instructs you to ask the user a questi...