Generate timestamped markdown implementation plans for software development tasks.
npx skills add https://github.com/graniet/kheish --skill plan-graniet
Please help me install this Agent Skill. Skill: plan Source: https://github.com/graniet/kheish/tree/main/skills/software-development/plan Command: npx skills add https://github.com/graniet/kheish --skill plan-graniet
This Skill eliminates the risk of jumping into unstructured software implementation that leads to wasted development effort, misaligned work, and avoidable rework by enforcing a planning-first workflow.
.kheish/plans/ directory for persistent tracking and reference.Use the plan skill to map out step-by-step implementation steps for adding a user profile editing feature to the existing account management system.
High-intent search queries and answers about installing and using this skill.
To generate a software development implementation plan, map out step-by-step execution steps, assess potential file changes, and define validation criteria before writing code. This process outputs persistent, timestamped markdown plans stored in a standardized workspace directory.
Unstructured coding leads to wasted effort and rework by skipping planning. Enforcing a planning-first workflow reviews existing codebase context to ensure steps are accurate, realistic, and aligned with the current project state before any code is written.
The best way to map out required file changes is through read-only context inspection that reviews your existing codebase without modifying files. This ensures development plans are accurate, realistic, and aligned with the current project state.
No, the code planning process performs read-only context inspection without modifying existing project files. It reviews the codebase to ensure generated implementation plans are accurate, realistic, and aligned with the current project state before execution begins.
Generated markdown plans are stored directly in your workspace's standardized `.kheish/plans/` directory. This ensures persistent tracking and reference for your software engineering workflow without modifying your existing codebase files.
Yes, you can define test validation steps for a new payment integration before implementation. The planning process maps out required file changes, validation criteria, and potential risks to prevent wasted development effort and avoidable rework.
cnfjlhjGather project and environment context using Grep, Glob, Read, Bash, and WebSearch before asking clarifying questions.
SriRamkunamsettyGenerate timestamped Markdown plans saved under .hermes/plans/ without executing code.
yash-gargImplement software changes from product requirements with testing and review.
webdevtodayjasonGenerate timestamped markdown project plans in the .hermes/plans/ directory.