rc-fix-analysislisted

# Fix From Analysis Execute the implementation plan produced by `rc-analyze`. This skill is the write-side counterpart of `rc-analyze`: it does not investigate or re-plan — it reads the plan from an existing analysis report and turns it into working, verified code. It is standalone and stack-agnostic; it detects the stack and works in that stack's idioms. ## Code navigation & editing (Serena) If the Serena MCP is available, prefer its symbolic tools over whole-file reads and line-based edits — 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 before changing a symbol (impact analysis). - `replace_symbol_body`, `insert_after_symbol`, `insert_before_symbol` for precise edits that don't depend on line numbers. Fall back to Grep/Glob + Read/Edit when Serena is unavailable or for plain-text (non-symbol) searches. ## Required Inputs - The path to the `rc-analyze` report to execute, or enough context to locate the most recent one (a feature slug or topic). The report must contain an **Implementation plan** section. - Optional: a scope to limit which plan steps to apply (specific steps, files, or directories). ## 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`