skills.rest
AGMO-Inc
AGMO-IncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

save-impl

Archive implementation summaries to an Obsidian vault with linked plan references.

4|1|Updated Mar 19, 2026
Search Tags:#implementation#obsidian#save#vault#archiving#project-management#linking-plans
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill save-impl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save-impl
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/save-impl
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill save-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams preserve implementation summaries by auto-archiving them to an Obsidian vault after execution completes, ensuring a durable, centralized record.

Core Features & Use Cases

  • Auto-collects project context (project name, owner) and git details
  • Creates a linked, indexed vault note with an implementation summary and related plan references
  • Updates project indexes and bidirectional plan links to keep the knowledge graph consistent
  • Optional: triggers lightweight wiki capture for long-term documentation traceability

Quick Start

Trigger the save implementation workflow to archive the summary in the Obsidian vault after execution completes.

Frequently Asked Questions about save-impl

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

FAQPage Schema
How do I auto-save implementation summaries to an Obsidian vault?▼

Auto-saving implementation summaries to an Obsidian vault requires triggering an archivist workflow that collects project context and git details, then creates an indexed note with bidirectional links to related plans.

How does archiving project context in Obsidian work for software teams?▼

Archiving project context works by collecting git details and project ownership data, creating indexed vault notes, and updating bidirectional plan links to maintain a centralized, durable knowledge graph across software projects.

Can I use Obsidian to create bidirectional links between implementation summaries and project plans?▼

Yes, you can use Obsidian to create bidirectional links by archiving implementation summaries as indexed notes, which automatically establish and update bidirectional references to their related project plans.

What is the best way to maintain a centralized change history in an Obsidian vault?▼

The best way to maintain a centralized change history is to automate archiving after execution completes, ensuring implementation summaries auto-collect git details and update project indexes for consistent knowledge graph traceability.

Do I need specific archivist workflows to save implementation summaries to Obsidian?▼

Yes, saving implementation summaries relies on archivist workflows and scripts like identify-project, collect-git-info, vault-save, and vault-update to gather data and establish notes with bidirectional links.

When should I not use automated archiving for project management in Obsidian?▼

Automated archiving is not suited for environments lacking git repositories or Obsidian vaults, as the process fundamentally depends on collecting git details and writing to vault structures to generate linked project indexes.

Related Skills

Explore More Software Engineering Skills→
pax-kpax-k
6

wiki-setup

Initialize an Obsidian wiki vault with directory structure and configuration.

Community
Intermediate
ThuHuynh1438ThuHuynh1438

meet

Transform raw meeting notes into structured notes with extracted decisions, blockers, and action items.

Community
Advanced
kirakuiinkirakuiin

ingest

Convert conversations or pasted documents into persistent session records.

Community
Advanced
venom9833venom9833

vercel-cli-with-tokens

Automate Vercel project deployment and management using token-based authentication.

Community
Intermediate