create-plan

Generate plan documents with unique identifiers and standardized frontmatter in .agents/plans.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/LKPioniere/lohnlab-esign --skill create-plan-lkpioniere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/LKPioniere/lohnlab-esign/tree/main/.agents/skills/create-plan
Command: npx skills add https://github.com/LKPioniere/lohnlab-esign --skill create-plan-lkpioniere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating plan documents in a consistent, scalable way can be error-prone and time-consuming. This skill ensures every new plan is generated with a unique three-word identifier, standardized frontmatter, and a properly formatted title, stored in the .agents/plans/ directory.

Core Features & Use Cases

  • Generate a unique three-word identifier for each new plan (e.g., happy-blue-moon).
  • Create frontmatter with the current date and a formatted title, plus a content body provided by the user.
  • Output to the .agents/plans/ directory with a predictable filename pattern {three-word-id}-{slug}.md.
  • Use Case: When starting work on a new feature, generate a ready-to-edit plan file with metadata and a clear, human-friendly title.

Quick Start

Run the create-plan script with a feature slug and plan content to generate a new plan file in .agents/plans/.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create markdown plan files with consistent frontmatter for project management?

To create markdown plan files with consistent frontmatter, use this skill to generate documents with a unique three-word identifier, current date metadata, and a slug-based filename pattern in the .agents/plans/ directory.

What is the best way to generate unique identifiers for feature planning documents?

The best way to generate unique identifiers for feature planning documents is using an automated tool that creates a unique three-word ID, ensuring predictable filenames and standardized metadata for each new plan.

Can I automate plan document creation with standardized titles and dates?

Yes, you can automate plan document creation by providing a feature slug and content body, which generates a markdown file with a formatted title, current date frontmatter, and a unique three-word identifier.

Does this plan generation tool require any dependencies to output markdown files?

No, this plan generation tool requires no dependencies to output markdown files, operating independently to create standardized plan documents with frontmatter and slug-based filenames in your project directory.

Why do my project plan files lack consistent naming patterns and metadata?

Your project plan files lack consistent naming patterns and metadata because manual creation is error-prone, whereas an automated planning skill enforces a predictable {three-word-id}-{slug}.md pattern and standardized frontmatter.