Plan-site

Enforce a structured planning and verification cycle for site refactoring.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DemumuMind/mcp-site-upload --skill plan-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plan-site
Source: https://github.com/DemumuMind/mcp-site-upload/tree/main/Plan-site
Command: npx skills add https://github.com/DemumuMind/mcp-site-upload --skill plan-site

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for a rigorous and repeatable process in planning and refactoring website code, preventing guesswork and ensuring thorough consideration of all aspects before implementation.

Core Features & Use Cases

  • Mandatory Planning Loop: Enforces a strict Plan -> Check -> Plan -> Final Verification cycle.
  • Detailed Planning Requirements: Outlines essential elements for Plan v1, including Hypothesis, Success Criteria, Scope, Architecture, Implementation Steps, Test Scenarios, Risks, and Rollback.
  • Fact-Checking: Emphasizes verifying assumptions during the Check phase.
  • Decision Completeness: Ensures Plan v2 is comprehensive enough to avoid new architectural decisions during implementation.
  • Multi-Side Thinking: Promotes consideration of Product Value, Architecture, Data, Security, Performance, SEO, Operations, and Delivery Risk.
  • Use Case: Before starting a significant refactor of the catalog page, use this Skill to ensure all potential impacts and implementation details are meticulously planned and verified.

Quick Start

Use the Plan-site skill to initiate a new refactoring plan for the user authentication flow.

Frequently Asked Questions about Plan-site

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

FAQPage Schema
How do I plan a website refactoring project to avoid architectural surprises during implementation?

Website refactoring planning requires a structured multi-stage loop mandating explicit hypotheses, success criteria, architecture, and risk assessments. This process ensures the final plan is comprehensive enough to avoid new architectural decisions during implementation.

What should be included in a site development plan before starting feature implementation?

A site development plan must include explicit hypotheses, scope, architecture, implementation steps, test scenarios, risks, and rollback procedures. Fact-checking assumptions and multi-side thinking across product value, security, and SEO are also mandatory.

How does a mandatory planning loop work for repository work and feature implementation?

A mandatory planning loop enforces a strict Plan, Check, Plan, Final Verification cycle for repository work. It mandates fact-checking assumptions during the Check phase to verify hypotheses before finalizing the implementation steps.

Can I use structured planning for site development on any scale of catalog page refactor?

Structured planning for site development suits significant refactoring tasks like a catalog page or authentication flow. It rigorously evaluates product value, architecture, data, security, performance, SEO, operations, and delivery risk before implementation.

Why do I need to verify assumptions and establish rollback procedures for site refactoring?

Verifying assumptions and establishing rollback procedures for site refactoring prevents guesswork and ensures thorough consideration of all impacts. Fact-checking validates hypotheses during the Check phase to mitigate delivery risks before implementation begins.