local-plan-standards

Enforce project planning constraints and plan-review rules for skills and plugins.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tvishwanadha/skills --skill local-plan-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-plan-standards
Source: https://github.com/tvishwanadha/skills/tree/main/.claude/skills/local-plan-standards
Command: npx skills add https://github.com/tvishwanadha/skills --skill local-plan-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and standardize the creation and review process for skills and plugins, preventing drift and ensuring compliance with marketplace requirements.

Core Features & Use Cases

  • Defines required frontmatter and content structure for skills.
  • Enforces marketplace registration and README updates across plugins.
  • Guides plan reviews with a formal verification step to catch inconsistencies early.

Quick Start

Run the plan-review process against the local-plan-standards to verify constraints before submission.

Frequently Asked Questions about local-plan-standards

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

FAQPage Schema
How do I enforce project planning standards for plugin development?

You can enforce project planning standards by running an automated verification process that checks plugin development constraints, ensuring marketplace registrations and README updates are compliant before submission.

What is a plan-verification step for marketplace plugin reviews?

A plan-verification step is a formal review process that checks on-disk component references and YAML frontmatter to catch inconsistencies and ensure plugins meet marketplace requirements early.

How do I verify YAML frontmatter contains required fields for skills?

To verify YAML frontmatter, run a plan review that checks the file structure to ensure it contains both a name and description, preventing drift and ensuring compliance with skill standards.

What directories are recognized as optional during plan reviews?

During plan reviews, the process recognizes scripts, references, and assets as optional directories, verifying on-disk component references while enforcing required content structure.

Does this plan review tool require any external dependencies to run?

No, the plan review tool does not require external dependencies to run, allowing you to directly verify local planning constraints and review rules for skills and plugins.

When do I need to run a plan-review process for my skills?

You need to run a plan-review process when preparing skills and plugins for submission, ensuring all marketplace registrations and README updates are verified against local planning standards.