[FEATURE] Native XLSX/DOCX read/edit tools (or official MCP server)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Working with Office documents requires generating Python/PowerShell scripts each time. This adds 30-60 seconds and tokens per operation. Maintaining MD/CSV as "source" with XLSX/DOCX as "output" creates data integrity issues (version drift, ambiguous source of truth).

Proposed Solution

Native tools for Claude Code:

• xlsx_read(path, sheet?, range?) → structured table data
• xlsx_edit(path, cell, value) → edit cell directly
• xlsx_find_row(path, column, value) → find and return row
• docx_read(path) → structured content with heading hierarchy
• docx_insert_after(path, heading, content) → insert content
• docx_replace(path, find, replace) → find/replace

Alternative Solutions

Alternative:
An official MCP server wrapping openpyxl/python-docx would achieve the same result via the existing extensibility mechanism.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Use Case:
Systems engineering project generated 40 requirements in XLSX + 6-page executive summary in DOCX. Every edit required script generation. With native tools, edits like "move REQ-X from L2 to L1"
would be a single tool call.

Additional Context

_No response_