create-plan

Generate Markdown plan files with frontmatter metadata under .agents/plans/.

1.8k|62|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/LibPDF-js/core --skill create-plan-libpdf-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/LibPDF-js/core/tree/main/.opencode/skills/create-plan
Command: npx skills add https://github.com/LibPDF-js/core --skill create-plan-libpdf-js

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of planning documents by templating new plan files and ensuring consistent metadata for each plan.

Core Features & Use Cases

  • Generate a unique three-word ID and create a new Markdown plan in .agents/plans/
  • Auto-fill frontmatter (date, title, slug) and provide a ready-to-edit blueprint for proposals
  • Use case: a product team drafts a feature plan and stores it in the shared plans folder for alignment

Quick Start

Run bun scripts/create-plan.ts "<slug>" "Your plan content here"

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I automate project planning documentation with standardized markdown frontmatter?

To automate planning documentation, you can generate a new markdown plan file with standardized frontmatter metadata like date, title, and slug. This ensures consistent metadata for product, architecture, and feature initiatives by templating content automatically.

How do I create a new plan file and auto-generate a unique slug for roadmapping?

You create a plan file by running a script that accepts a slug and plan content, which then saves the markdown file under the .agents/plans/ directory. The process guides slug creation and auto-fills the required frontmatter metadata.

Can I use this to standardize feature plans for my product team's shared folder?

Yes, you can standardize feature plans for a product team by generating deterministic metadata and storing the resulting plan files in a shared folder. This enforces alignment by providing a ready-to-edit blueprint for proposals.

What is the best way to maintain consistent metadata across multiple project management plan files?

The best way to maintain consistent metadata is to use an automated scripting approach that enforces deterministic standards for date, title, and slug fields. This prevents manual entry errors and standardizes the planning documentation across your project.

Do I need any dependencies to generate frontmatter metadata for plan files?

No dependencies are required to generate frontmatter metadata for plan files. The skill operates independently using a standalone script to handle content curation, slug generation, and file creation without external packages.