Create a markdown implementation plan with read-only repository review.
npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill plan-hungthinh04
Please help me install this Agent Skill. Skill: plan Source: https://github.com/hungthinh04/Hermes_AI_Agent/tree/main/skills/software-development/plan Command: npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill plan-hungthinh04
This Skill helps you design a clear implementation plan before making changes, so you can coordinate work without editing code or running actions.
Ask the assistant to create a detailed implementation plan for your task and save it as a markdown file under .hermes/plans/.
High-intent search queries and answers about installing and using this skill.
To create an implementation plan without modifying the codebase, you can generate a detailed markdown file capturing goals, steps, and risks. This read-only workflow inspects the repository safely and saves the plan under .hermes/plans/ without executing code.
Yes, you can scope out bug fixes and workflow design without running code or making commits. This planning approach performs a safe repository review and outputs a markdown plan with explicit validation steps while preserving a strictly read-only environment.
The best way to document task assumptions and file paths before a refactor is to produce a structured markdown implementation plan. It captures goals, assumptions, targeted file paths, and validation notes to coordinate the work clearly before any changes occur.
Yes, this planning workflow supports read-only repository review for software engineering tasks. It allows you to inspect the codebase and design step-by-step coordination for features or fixes while avoiding mutations, commits, and external actions.
When scoping software engineering work, markdown implementation plans are saved under the .hermes/plans/ directory. This ensures your task coordination details, including risk notes and validation steps, are stored in a dedicated location.
The main limitation of this markdown planning workflow is that it does not execute code or modify project files. It is designed strictly for scoping and validation, meaning you must implement the actual feature changes separately after the plan is finalized.
JKhyroCreate a markdown implementation plan with steps, file targets, and risk notes.
ddobrinCompare codebases against implementation plans and generate markdown audit reports.
ActiveInferenceInstituteParse GNN Markdown files and serialize structured model data to JSON, YAML, and XML.
TheycallmehollaSynchronize local skill directories with a remote repository while preserving state files.
