mcp-builder-phase-1-deep-research-and-planning
Sub-skill of mcp-builder: Phase 1: Deep Research and Planning (+3).
Best use case
mcp-builder-phase-1-deep-research-and-planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of mcp-builder: Phase 1: Deep Research and Planning (+3).
Teams using mcp-builder-phase-1-deep-research-and-planning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/phase-1-deep-research-and-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mcp-builder-phase-1-deep-research-and-planning Compares
| Feature / Agent | mcp-builder-phase-1-deep-research-and-planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of mcp-builder: Phase 1: Deep Research and Planning (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Phase 1: Deep Research and Planning (+3) ## Phase 1: Deep Research and Planning **Study MCP Design Principles:** - Balance "API coverage vs. workflow tools" - Review MCP protocol at modelcontextprotocol.io - Learn framework specifics (TypeScript recommended) - Analyze target API endpoints **Key Questions:** 1. What actions does the user want to perform? 2. What API endpoints are available? 3. Which operations are read-only vs destructive? 4. How should errors be handled? ## Phase 2: Implementation **Project Setup (TypeScript):** ```bash mkdir my-mcp-server cd my-mcp-server npm init -y npm install @modelcontextprotocol/sdk zod npm install -D typescript @types/node ``` **tsconfig.json:** *See sub-skills for full details.* ## Phase 3: Review and Test **Code Quality Checklist:** - [ ] No code duplication - [ ] Full type coverage - [ ] Proper error handling - [ ] Input validation - [ ] Rate limiting (if needed) **Testing with MCP Inspector:** ```bash npx @modelcontextprotocol/inspector node dist/index.js ``` ## Phase 4: Create Evaluations Generate 10 complex, realistic test questions: - Independent (no dependencies between questions) - Read-only (don't modify external state) - Verifiable (clear expected answers)
Related Skills
external-drive-ingest-planning
Plan safe external-drive ingests into repo-aligned storage such as /mnt/ace: read-only mounts, manifests, staged rsync, dedupe-merge gates, GitHub issue traceability, and governance/execution split.
planning-lane-cross-review-permission-fallback
Handle overnight planning-only lanes where plan revision/editing works but real cross-provider review dispatch is permission-blocked.
overnight-planning-noop-run-salvage
Recover when unattended overnight Codex planning runs exit 0 but produce no required artifacts; salvage the wave by auditing existing plan state, generating missing summary artifacts manually, and preserving morning monitoring surfaces.
large-parallel-planning-wave-environment-failure-handoff
Handle large pre-plan-review planning waves that succeed analytically but fail to persist artifacts due to quota exhaustion, sandbox write failures, or cancelled GitHub mutations.
gtm-prospect-pipeline-phased-execution
Phased execution pattern for
github-visual-planning-issues
Create review-friendly GitHub planning issues that supersede stale/seasonal issues and include source-backed image thumbnails for faster human review.
planning-goal
Goal-Oriented Action Planning (GOAP) specialist that dynamically creates intelligent plans to achieve complex objectives. Use for multi-step tasks with dependencies, adaptive replanning, complex deployment workflows, or when a high-level goal needs systematic breakdown into achievable actions.
planning-code-goal
Code-centric Goal-Oriented Action Planning integrated with SPARC methodology. Use for feature implementation planning, performance optimization goals, testing strategy development, or any software development objective requiring systematic breakdown with measurable success criteria.
mcp-builder
Guide for building high-quality Model Context Protocol (MCP) servers that allow LLMs to interact with external services. Use when creating new MCP integrations, tools, or servers for Codex or other AI systems.
research-literature
Systematize research and literature gathering for engineering categories — queries doc index, capability map, and standards ledger to produce structured research briefs for calculation implementation. type: reference
research-and-literature-gathering
Systematic workflow for finding, downloading, and indexing engineering literature by domain. Covers the full lifecycle: discovery via standards ledger and doc index, web search for open-access PDFs, download script generation, PDF validation, catalogue YAML creation, and handoff to the 7-phase document-index-pipeline for indexing. Use when populating a new engineering domain with reference literature or when a WRK item requires domain-specific standards and textbooks.
rag-system-builder
Build Retrieval-Augmented Generation (RAG) Q&A systems with Codex or OpenAI. Use for creating AI assistants that answer questions from document collections, technical libraries, or knowledge bases.