plan-creating-project-plans

Enforce standardized structure and design-decision validation for project plans.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill plan-creating-project-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-creating-project-plans
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/plan-creating-project-plans
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill plan-creating-project-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about plan-creating-project-plans

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

FAQPage Schema
How do I create an agent-executable project plan with TDD and Gherkin test cases?

To create an agent-executable project plan, enforce standardized directory structures, explicit file paths, verifiable shell commands, and Gherkin acceptance criteria. This ensures AI agents can execute tasks directly without manual interpretation or costly rework.

What is the best way to enforce project plan standards in an OSE-style monorepo?

Enforcing project plan standards in an OSE-style monorepo requires stage-aware naming conventions, mandatory multi-file layouts, and pre-write design-decision validation gates. This eliminates inconsistent, unexecutable plans across ideation, backlog, and execution workflows.

How do validation gates work when creating structured project plans?

Validation gates work by applying structured multiple-choice grilling before writing plan content and after drafting. This resolves design decisions with stakeholders upfront, ensuring plans are aligned with stakeholder intent and free of ambiguity.

Do I need phase-based pause safety gates for in-progress execution planning?

Yes, phase-based pause safety gates are mandatory for in-progress execution planning. They ensure traceable, agent-executable plans by enforcing observable acceptance criteria, TDD-shaped cycles, and explicit [AI]/[HUMAN] executor tagging for every checklist item.

Can I use a single-file layout for trivial project plans instead of a multi-file structure?

Yes, trivial project plans can use a single-file README.md layout instead of the mandatory five-document multi-file structure. Substantive plans require the full multi-file layout to maintain execution-grade clarity and strict quality guardrails.

Why does my project plan fail automated validation checks in a monorepo?

Project plans fail automated validation checks due to missing explicit file paths, verbatim shell commands, or observable acceptance criteria. Enforcing standardized directory layouts and stage-aware naming conventions ensures plans pass quality guardrails.