create-plan

Creates standardized plan files with unique three-word identifiers and frontmatter in .agents/plans/.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/GitLaw-co/documenso --skill create-plan-gitlaw-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/GitLaw-co/documenso/tree/main/.agents/skills/create-plan
Command: npx skills add https://github.com/GitLaw-co/documenso --skill create-plan-gitlaw-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of standardized plan files in .agents/plans/, ensuring each file uses a unique three-word identifier, proper frontmatter, and a formatted title.

Core Features & Use Cases

  • Generates a reproducible file name combining a three-word slug with a short slug.
  • Writes frontmatter including date and formatted title, enabling consistent metadata for planning tasks.
  • Accepts user-provided content to populate the plan document for sprint planning, feature scoping, or project initiation.

Quick Start

Run the script with a slug and content to generate a new plan file.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I automate plan file creation with consistent naming and frontmatter?

Automating plan file creation involves generating files in a designated directory using a unique three-word slug for the filename and embedding structured frontmatter with the date and formatted title to ensure metadata consistency.

What is a three-word slug identifier for project planning documents?

A three-word slug identifier is a reproducible naming convention enforced during plan file creation, ensuring each document in the planning directory has a unique, standardized, and easily referenceable filename.

Can I use custom content for sprint planning when generating a plan file?

Yes, you can provide custom content to populate the plan document for sprint planning, feature scoping, or project initiation, which is then written alongside the standardized frontmatter and unique filename.

Does plan file generation require specific directory structures for metadata organization?

Plan file generation requires a specific directory structure, typically `.agents/plans/`, to store the newly created files, ensuring all planning documents and their associated frontmatter metadata are centralized.

What metadata is included in the frontmatter of generated plan files?

The frontmatter in generated plan files includes the creation date and a formatted title, providing consistent metadata for tracking and organizing planning tasks across different projects.

When do I need standardized file naming with slugs for feature scoping?

Standardized file naming with slugs is needed when organizing features, tasks, or projects requires consistent identification, enabling automated tracking and preventing filename collisions during feature scoping.