mcp-implement-plan

Implement approved plans with test-backed changes on the develop branch.

2|Updated Feb 3, 2026

Search Tags:#typescript #implementation #mcp #test-driven #code-review #plan-management #engineering-workflow

Ready to run

npx skills add https://github.com/stackconsult/RE-Engine --skill mcp-implement-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-implement-plan
Source: https://github.com/stackconsult/RE-Engine/tree/main/.windsurf/skills/mcp-implement-plan
Command: npx skills add https://github.com/stackconsult/RE-Engine --skill mcp-implement-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically implement approved plans using small, test-backed changes that respect RE-Engine's architecture, TypeScript strict mode, and production deployment requirements.

Core Features & Use Cases

Iterative, test-backed implementation following an approved plan with frequent commits.
Strict adherence to RE-Engine architecture and MCP integration patterns.
Comprehensive testing strategy including unit, integration, and cross-component validation, plus documentation updates.

Quick Start

Start by opening an approved plan in plans/YYYY-MM-DD-target.md and implement changes iteratively with tests on the develop branch.

Frequently Asked Questions about mcp-implement-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I systematically implement an approved plan with test-driven TypeScript?▼

Systematic plan implementation applies small, test-backed changes iteratively to ensure strict TypeScript compliance. It executes approved plans step-by-step, verifying environment setup, cross-component features, and frequent commits.

What is the best way to manage an engineering workflow for cross-component feature rollouts?▼

Engineering workflow management orchestrates plan execution by applying verifiable changes that respect architecture boundaries. It handles step-by-step feature rollouts, ensuring iterative development, testing, and code review are completed sequentially.

Does MCP integration support iterative development with frequent commits?▼

MCP integration supports iterative development by orchestrating frequent, verifiable commits alongside MCP tool updates. The process ensures production deployment requirements are met while maintaining strict adherence to integration patterns.

How do I apply test-driven development for MCP backend deployments?▼

Test-driven deployment applies a comprehensive testing strategy including unit and integration tests before backend deployment. It validates cross-component interactions and updates documentation iteratively on the develop branch.

When do I need plan management for engineering backend deployments?▼

Plan management is needed when executing approved plans in plans/YYYY-MM-DD-target.md for backend deployments. It ensures step-by-step changes respect architecture, environment setup is complete, and code review is performed iteratively.

What are the limitations of plan-driven implementation for MCP tool updates?▼

Plan-driven implementation requires an approved plan file and strict adherence to architecture, limiting ad-hoc changes. It is not suited for rapid prototyping outside the test-backed, iterative development workflow defined in the execution guide.