Save planning outputs as Markdown files under project and branch paths.
npx skills add https://github.com/uuta/dotfiles --skill plan-on-md
Please help me install this Agent Skill. Skill: plan-on-md Source: https://github.com/uuta/dotfiles/tree/main/skills/plan-on-md Command: npx skills add https://github.com/uuta/dotfiles --skill plan-on-md
This Skill automates saving planning outputs as local Markdown files, enabling seamless archival and retrieval of plans created in plan mode.
Plan and save a new plan named 'middleware-refactor-plan' for project 'curry' on branch 'feature/#468' to the path ~/uuta/Projects/curry/468/middleware-refactor-plan.md.
High-intent search queries and answers about installing and using this skill.
To save plan mode output as a local Markdown file, the Skill automatically writes planning outputs to a structured path under ~/uuta/Projects/{project}/{branch}/{file}.md. It handles path derivation, file naming, and content preservation without requiring external tooling.
When saving Markdown plans, project names are normalized by removing trailing numeric suffixes, and branch names are simplified to concise numeric identifiers. For example, branch 'feature/#468' becomes '468' in the file path.
No external tools or dependencies are required to save plans to Markdown. The Skill handles path derivation, file naming, and content preservation entirely on its own, satisfying local Markdown archival needs directly.
The best way to organize project plans by feature branches is using a standardized file path structure. This Skill groups plans under ~/uuta/Projects/{project_name}/{branch_name}/, keeping decisions easy to locate, review, and reference.
Yes, you can use this Markdown plan saving workflow for any project-based workflow where plans are created in plan mode. It targets project-based workflows by normalizing project names and simplifying branch names for consistent local storage.
Project names have trailing numeric suffixes removed in the saved Markdown path to normalize naming conventions. This ensures consistent directory structures, preventing duplicate or fragmented project folders caused by version numbers.
shankurLog work sessions and push Markdown summaries to the ai-history repository.
revfactoryRead, parse, and convert HWP/HWPX documents to Markdown or other formats.
sheawinklerGenerate a timestamped Markdown plan and save it under .hermes/plans/.
htayjRecord, organize, and search notes and decisions in a local vault.
