Manage Codex plan documents stored under CODEX_HOME/plans.
npx skills add https://github.com/ale-alfaro/dotfiles --skill plan-ale-alfaro
Please help me install this Agent Skill. Skill: plan Source: https://github.com/ale-alfaro/dotfiles/tree/main/common/.config/codex/skills/.system/plan Command: npx skills add https://github.com/ale-alfaro/dotfiles --skill plan-ale-alfaro
Plan lifecycle management for Codex plans on disk, enabling creation, retrieval, updates, deletions, and organized storage for implementation work or reference documentation.
Stash a new plan by providing its name, description, and body to store the frontmatter under CODEX_HOME/plans.
High-intent search queries and answers about installing and using this skill.
Plan management for Codex plans handles creating, reading, updating, and deleting plan documents stored under CODEX_HOME/plans. Each plan uses frontmatter metadata with required name and description fields, defaults to ~/.codex/plans, and supports implementation or reference documentation.
Centralizing markdown project plans is handled by storing them as frontmatter documents under CODEX_HOME/plans. This approach keeps architecture notes and implementation work organized, allowing dedicated scripts to list, find, and validate plan metadata efficiently.
Yes, you can stash implementation plans by providing a name, description, and body to store frontmatter metadata under CODEX_HOME/plans. Dedicated scripts then validate frontmatter and discover plan metadata to retrieve, read, or update the documents.
No dependencies are required to use Codex plan management for storing documents. The system operates independently using scripts to manage plan files with frontmatter metadata, defaulting to the ~/.codex/plans directory without needing external packages.
Finding and validating existing plan metadata in CODEX_HOME/plans is done via dedicated scripts. These scripts list, find, and reference plans by validating the required frontmatter fields, ensuring name and description metadata are correctly structured.
Frontmatter plan files should be used when you need structured lifecycle management for implementation work or overview reference. Unlike standard markdown, they enforce required name and description metadata, enabling programmatic discovery, validation, and organized storage under CODEX_HOME/plans.
eduardoabreu81Create a standardized SKILL.md structure with name and description frontmatter fields.
akiojinGenerate structured plans with YAML frontmatter for software projects.
damidaniGenerate uniquely identified markdown project plan files with standardized frontmatter.
nachopalmeriOrganize Obsidian vaults with PARA, Zettelkasten, MOCs, and templates.
