recce-mcp-dev

To package MCP server development workflows into an auditable skill, load the upstream playbook and support-pack to guide execution while preserving source provenance and bundling review artifacts like checklists and rubrics.

Provenance tracking for MCP tool handlers preserves the origin of upstream source material during modification, enabling reviewers to audit imports and reason about routing decisions while staying connected to original context.

Yes, you can use this workflow to modify MCP-related tests and server code. It applies specifically when altering MCP server code, tool handlers, or tests, packaging these changes with bundled guidance for reviewers.

Artifacts included for reviewers auditing MCP development intake are a checklist, rubric, playbook, prompt template, router note, and source manifest, ensuring full visibility of upstream provenance and routing logic.

You need to preserve upstream provenance during MCP development when importing and modifying upstream source material into a native skill surface, ensuring that public intake packaging and routing decisions remain auditable for reviewers.

Yes, this skill surface works without external dependencies for MCP routing. It natively bundles router guidance, a source manifest, and a playbook to support routing decisions and review handoff independently.