rc-create-taskslisted

# Create Tasks Decompose requirements into detailed, actionable task files with codebase-informed enrichment. ## Code navigation (Serena) If the Serena MCP is available, prefer its symbolic tools over whole-file reads when enriching tasks from the codebase — they are LSP-accurate and token-efficient: - `get_symbols_overview` to grasp a file's structure before reading it; `find_symbol` (by name path, e.g. `Type/method`) to jump straight to a definition. - `find_referencing_symbols` to map every caller of a symbol before reasoning about impact. Fall back to Grep/Glob + Read when Serena is unavailable or for plain-text (non-symbol) searches. ## Required Inputs - Feature name identifying the `.rc/tasks/<name>/` directory. - At minimum, `_prd.md` or `_techspec.md` in that directory. ## 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** — select t