myco:plan-persistence-and-agent-directed-capture

Persist Myco plans deterministically and deduplicate across channels via MCP tools.

12|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/goondocks-co/myco --skill myco-plan-persistence-and-agent-directed-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myco:plan-persistence-and-agent-directed-capture
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/plan-persistence-and-agent-directed-capture
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-plan-persistence-and-agent-directed-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan capture and persistence across multiple channels is automated and deterministic, ensuring consistent identity and provenance for plans generated by agents, transcripts, and file-based sources, while enabling reliable deduplication and lineage.

Core Features & Use Cases

  • Logical-key identity models to deduplicate plans across channels
  • MCP tool integration for agent-directed plan capture
  • Unified plan-capture helper with provenance and search integration
  • Plan lineage and cross-source reconciliation for auditability

Quick Start

Install and configure the plan persistence module, then start capturing plans with the myco_save_plan MCP tool in an active session.

Frequently Asked Questions about myco:plan-persistence-and-agent-directed-capture

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

FAQPage Schema
How do I deduplicate agent-generated plans across different capture channels?

Plan deduplication across channels uses logical-key identity models to consistently identify and reconcile plans from transcripts, file-system ingestion, and agent-directed captures. This ensures reliable lineage and prevents duplicate entries.

What is deterministic plan persistence for multi-agent workflows?

Deterministic plan persistence automates saving plans generated by agents and transcripts with consistent identity and provenance. It ensures reliable deduplication and lineage tracking across cross-channel sources for auditability.

Can I use MCP tools for agent-directed plan capture in active sessions?

Yes, agent-directed plan capture uses defined MCP tools like the myco_save_plan helper. You can install and configure the persistence module to start capturing plans with provenance directly within an active session.

How do I track provenance and lineage for plans ingested from files?

Plan lineage and provenance tracking are integrated into a unified capture helper. This tracks the origin of file-system plan ingestion and reconciles it across sources for full auditability and multi-agent collaboration.

Does plan persistence support transcript mining and search integration?

Yes, transcript mining is a supported capture channel. The module integrates plan capture with search capabilities, enabling consistent retrieval and cross-source reconciliation of plans mined from session transcripts.

What is the best way to ensure consistent plan identity across multi-agent collaborations?

Applying logical-key identity models is the best way to ensure consistent plan identity. This approach deduplicates plans across channels and enables reliable multi-agent collaboration and lineage tracking.