save-plan

Save plan data to the Obsidian vault with index updates and cleanup.

4|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill save-plan-agmo-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-plan
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/save-plan
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill save-plan-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a manual fallback to save plan data into the Obsidian vault when the plan skill's auto-save fails or is skipped, ensuring continuity and traceability of planning work.

Core Features & Use Cases

  • Manual vault save: Writes the current plan to the Obsidian vault with a consistent frontmatter schema.
  • Index integration: Updates plan indexes to surface saved plans for quick access.
  • Safety checks: Avoids duplicates and cleans up temporary artifacts after saving.

Quick Start

Trigger the Save Plan fallback to manually save the current plan to the Obsidian vault.

Frequently Asked Questions about save-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually back up plans to my Obsidian vault when auto-save fails?

To manually back up plans to your Obsidian vault, trigger the save fallback to write current plan data with a consistent frontmatter schema. This ensures continuity and traceability of planning work when automatic saving fails or is skipped.

Does saving plans to Obsidian update the project index automatically?

Yes, saving plans to Obsidian updates the plan indexes automatically to surface saved plans for quick access. The process integrates index updates directly within the manual vault save workflow.

What is the best way to avoid duplicate entries when backing up planning data to Obsidian?

The best way to avoid duplicate entries when backing up planning data to Obsidian is using built-in safety checks. The save process validates data to avoid duplicates before cleaning up temporary artifacts.

Can I use vault utilities to save drafted plans that require durable persistence in Obsidian?

Yes, you can use vault utilities to save drafted plans that require durable persistence in Obsidian. The process creates temporary files, saves data to the vault, updates project indexes, and removes temporary artifacts.

Why does the plan auto-save fail and require a manual vault save fallback?

Plan auto-save can fail due to various system interruptions, requiring a manual vault save fallback to ensure continuity. This fallback manually writes the current plan data to the Obsidian vault with a consistent frontmatter schema.