Generate timestamped Markdown implementation plans without modifying repository files.
npx skills add https://github.com/afel6/scal-ai-pipeline --skill plan-afel6
Please help me install this Agent Skill. Skill: plan Source: https://github.com/afel6/scal-ai-pipeline/tree/main/hermes_skills_library/software-development/plan Command: npx skills add https://github.com/afel6/scal-ai-pipeline --skill plan-afel6
Provides a safe, planning-only workflow for autonomous agents and engineers who need a concrete, reviewable plan before any code changes or executions are performed.
Write a timestamped markdown plan for the requested task and save it to .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md.
High-intent search queries and answers about installing and using this skill.
A non-mutating development plan is generated by inspecting repository context read-only and saving a Markdown plan without modifying files. This creates a reviewable document of goals and implementation strategies for handoff or staging before execution.
A read-only planning workflow is a process where an agent inspects repository context without making code changes, producing a saved plan for handoff or audit. It ensures safe, reviewable documentation of implementation strategies before any execution occurs.
Yes, you can create a step-by-step implementation plan without writing code by listing goals, assumptions, affected files, tests, and risks in a Markdown file. This provides a developer or sub-agent with a concrete strategy to execute later.
To save a timestamped plan for an engineering review, write the Markdown plan to a file formatted as .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md. This workspace-native output ensures plans are organized and traceable for audit purposes.
Yes, this planning workflow supports optional repository inspection to identify likely files to change before execution. It examines the repository context in read-only mode to determine which files will be affected by the proposed implementation strategy.
The limitation of plan-mode documentation is that it strictly adheres to non-mutating constraints, meaning it cannot perform code changes or run commands. It only produces a saved plan for staging and handoff, requiring a separate execution step afterward.
mindmorassAutomate development workspace provisioning with layered configuration and setup scripts.
nielpattinResolve Git merge conflicts with a structured plan and test validation.
dayvidphamStandardize review findings with severity classification via Beads CLI.
tomascorterealExecute trivial coding tasks directly without planning or subagent spawning.
