plan

To generate a structured project plan, this skill creates timestamped markdown files in your local workspace outlining goals, approaches, and step-by-step instructions. It requires read-only repository access to ensure proposed steps are technically feasible before implementation begins.

You need a markdown implementation plan when starting complex tasks like refactoring to prevent impulsive coding. It forces a structured planning phase to outline necessary changes, identify risks, and define validation steps before touching the codebase.

You cannot use this planning skill to modify files or execute terminal commands. It enforces read-only safety guardrails during the planning phase to prevent accidental file modification, ensuring your repository context remains untouched while generating the plan.

The best way to outline an actionable development workflow is generating a standardized markdown document with step-by-step instructions. This skill operates by creating timestamped plan files in the .adame/plans/ directory to guide subsequent development cycles accurately.

The generated markdown plan saves automatically to the .adame/plans/ directory within your local workspace. It creates timestamped plan files here to securely guide subsequent development cycles without altering the existing codebase structure.

The planning agent needs read-only repository access to ensure proposed implementation steps are accurate and technically feasible. By analyzing the existing codebase context safely, it generates a highly relevant and actionable markdown plan for your specific software development task.