project-planning

Name: project-planning
Availability: InStock
Author: mbelenmontoya

Create standardized project plan documents with phased implementation steps and guardrails.

Updated May 8, 2025

Search Tags:#planning #templates #documentation #docs #guardrails #project-management #implementation-steps

Ready to run

npx skills add https://github.com/mbelenmontoya/design-token-manager-api --skill project-planning-mbelenmontoya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-planning
Source: https://github.com/mbelenmontoya/design-token-manager-api/tree/main/.claude/skills/project-planning
Command: npx skills add https://github.com/mbelenmontoya/design-token-manager-api --skill project-planning-mbelenmontoya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized, structured project plan documents with consistent formatting, appropriate detail levels, and clear implementation steps.

Core Features & Use Cases

Structured plan templates that enforce consistent sections and executive summaries after each phase.
Phase-based Implementation Steps with guardrails to reduce scope creep and ensure traceability.
Clear documentation guidance stored under /docs with kebab-case filenames for easy discovery.

Quick Start

Create a new plan document in /docs using the exact template and fill in the required sections for your project.

Frequently Asked Questions about project-planning

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

FAQPage Schema

How do I create a standardized project plan document with clear implementation steps?▼

To create a standardized project plan, use a structured template that enforces consistent sections, phase-based implementation steps, and executive summaries. Store the plan under /docs/ with kebab-case filenames for easy discovery and distribution.

What is the best way to structure technical project plans for refactoring or migrations?▼

The best way to structure technical project plans is to organize implementation steps into distinct phases with guardrails. This reduces scope creep and ensures traceability for complex refactoring projects, migrations, or architectural decisions.

How do I prevent scope creep when writing documentation for architectural decisions?▼

Prevent scope creep in architectural decision documentation by applying guardrails within a phase-based implementation steps section. This enforces clear boundaries and ensures traceability throughout the project plan.

Can I use a standardized template for different types of technical features and migrations?▼

Yes, you can use a single standardized template for technical features, refactoring projects, migrations, and architectural decisions. It enforces consistent formatting and appropriate detail levels across all project types.

Do I need to include an executive summary in my project management documentation?▼

Yes, you need an executive summary in your project management documentation. The template requires generating executive summaries after each phase completion to ensure the plan is ready for distribution and review.

Where should I store project plan files for easy discovery in my repository?▼

Store project plan files under the /docs/ directory using kebab-case filenames. This standardizes documentation storage and ensures easy discovery for technical features and architectural decisions.