Inspect repository context and draft timestamped Markdown plans under .hermes/plans.
npx skills add https://github.com/loongclaw-ai/loongclaw --skill plan-loongclaw-ai
Please help me install this Agent Skill. Skill: plan Source: https://github.com/loongclaw-ai/loongclaw/tree/main/skills/plan Command: npx skills add https://github.com/loongclaw-ai/loongclaw --skill plan-loongclaw-ai
Without a planning mode, agents may prematurely edit files or run commands, creating noise before a strategy is settled. Plan mode isolates that stage by capturing actionable plans without risking unintended changes.
.hermes/plans/ with timestamped names so teammates can review and iterate.Write a plan that records the goal, current context, key steps, and verification strategy before starting the requested work.
High-intent search queries and answers about installing and using this skill.
Drafting a markdown plan without executing work is done by inspecting repository context in a read-only mode. This approach captures actionable strategies, recording goals, assumptions, and risks while preventing unintended file mutations or automated actions.
Creating a workflow strategy before automation involves isolating the planning stage to capture detailed deliverables. This method records goals, current context, key steps, and verification strategies into a markdown file for team review without risking premature edits.
Saving timestamped markdown plans requires writing output to a designated workspace-safe directory. The generated strategy files are stored with timestamped filenames, ensuring teammates can sequentially review and iterate on the recorded context and approaches.
Inspecting repository context to generate planning documents is possible under strict read-only restrictions. This allows the system to analyze existing files and strategy needs while explicitly forbidding any code edits, terminal mutations, or automated actions.
A planning workflow should include detailed deliverables such as goals, assumptions, approaches, affected files, tests, and risks. Recording these elements ensures clarity and comprehensive risk management before any actual execution work begins.
Automated workflows prematurely edit files when a planning mode is not enforced. Applying a plan-only approach isolates the strategy stage by capturing actionable steps in markdown, preventing noise and unintended changes before execution.
gatovillanoRead project memory context from llm_context.md for cross-session AI tasks.
breenglesConvert implementation plans into review-gated code changes with sequential commits.
OKHP3Convert AI-driven assets and ideas into standardized GitHub repositories.
buchananwillRestrict container agents to read-only Git operations on host repositories.