Generate a markdown implementation plan with file changes and tests.
npx skills add https://github.com/cabezno/bmb-encover-agent --skill plan-cabezno
Please help me install this Agent Skill. Skill: plan Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/software-development/plan Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill plan-cabezno
It helps you turn a request into a clear, concrete implementation plan without risking unintended code changes, running commands, or external actions.
.hermes/plans/ as a timestamped file so the plan is easy to reference later.Use the plan mode by asking for a plan for the task, then save it into the active workspace’s .hermes/plans/ directory.
High-intent search queries and answers about installing and using this skill.
An implementation plan for software development is generated as a concrete markdown file without executing code changes. It provides a staged workflow approach, including likely file changes and validation tests, saving the output to `.hermes/plans/`.
Documenting a workflow plan before modifying software involves generating a timestamped markdown file that captures goals, assumptions, step-by-step actions, and risk tradeoffs. This plan-only approach ensures alignment on scope without risking unintended code changes.
Creating a staged implementation plan that includes tests and file changes is the core function. The generated markdown deliverable explicitly lists likely file modifications, validation tests, open questions, and step-by-step workflow instructions.
The planning workflow saves deliverables directly to the workspace for later reference. Plans are persisted as timestamped markdown files in the `.hermes/plans/` directory, ensuring the implementation guide remains accessible and easy to track.
Using a plan-only approach prevents unintended code changes and avoids running external commands during the scoping phase. It turns a request into a clear, actionable implementation guide with defined tests and file changes before any development begins.
Limitations of generating markdown plans include strict plan-only behavior and read-only inspection. It cannot perform code changes, execute commands, or take external actions, functioning solely to produce a staged implementation guide.
coco-researchInitialize a project planning workspace with guided discovery and structured markdown deliverables.
DFilipeSExecute implementation plans by writing code, running tests, and committing changes.
OfirGavishCustomize NinjaClaw channels, triggers, and tool integrations end-to-end.
jumppad-labsGenerate structured implementation plans with code snippets, test strategies, and success criteria.