plan-creating-project-plans

What problem does it solve?

This Skill eliminates the risk of inconsistent, incomplete, or unexecutable project plans by enforcing standardized directory structure, stage-aware naming conventions, mandatory pre-write and post-write design-decision grilling gates, and strict quality guardrails that ensure plans are aligned with stakeholder intent and can be executed without costly rework.

Core Features & Use Cases

• Standardized Plan Structure: Enforces the official plans/ directory layout with stage-aware naming (backlog uses YYYY-MM-DD__identifier, in-progress uses identifier only, done uses YYYY-MM-DD__identifier) and mandatory five-document multi-file layout for substantive plans, or single-file README.md for trivial plans.
• Mandatory Decision Validation: Requires structured multiple-choice grilling gates before writing any plan content (pre-write) and after drafting (post-write) to resolve all design decisions with stakeholders, eliminating ambiguity and rework.
• Execution-Grade Clarity: Enforces explicit file paths, verbatim shell commands, and observable acceptance criteria for every delivery checklist item, plus mandatory [AI]/[HUMAN] executor tagging and TDD-shaped cycles for code-touching work.
• Use Case: A team building a new authentication feature can use this Skill to create a plan that passes all automated validation checks, has clear task ownership, and can be executed directly by AI agents without manual interpretation.

Quick Start

Ask the AI to create a new structured project plan for your upcoming feature, following all enforced naming, structure, and quality gate requirements.