create-plan

To create markdown plan files without filename conflicts, use an automated script that generates a unique three-word identifier appended to your provided slug. This produces collision-free Markdown documents with standardized frontmatter for team planning workflows.

Automating structured plan document creation for agents involves running a script that accepts a descriptive slug and content via arguments or heredoc. It generates metadata-rich Markdown files with a unique three-word ID, current date, and formatted title in the frontmatter.

The three-word identifier system prevents duplicate plan filenames by appending a uniquely generated three-word string to your provided slug. This guarantees filename uniqueness across feature proposals, task outlines, and agent-driven planning workflows without manual naming coordination.

Yes, you can pass markdown content to the plan creation script via heredoc or script arguments. The script processes the provided content and generates a timestamped Markdown plan file named with a three-word ID and slug pattern in the designated plans directory.

Yes, the generated plan file includes standard metadata frontmatter containing the current date and a formatted human-readable title. This standardized frontmatter ensures plans remain discoverable and consistently organized across team and agent planning workflows.

A limitation of automated slug-based plan file generation is that it produces files strictly in Markdown format within a specific directory structure. It is designed for feature proposals and task roadmaps, so it may not suit workflows requiring non-Markdown document formats or alternative storage paths.