tool-store

Store architectural decisions and TODO contexts with tags and cross-links.

2|Updated Apr 10, 2024
One-click install
npx skills add https://github.com/gdurandvadas/dotfiles --skill tool-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-store
Source: https://github.com/gdurandvadas/dotfiles/tree/main/config/opencode/skills/tool-store
Command: npx skills add https://github.com/gdurandvadas/dotfiles --skill tool-store

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stores architectural decisions, TODO-context references, and cross-links to preserve durable project knowledge across sessions and agents, enabling fast onboarding and auditability.

Core Features & Use Cases

  • Centralized memory for architectural decisions and TODO-context items with provenance.
  • Tagging, linking, and [store:<id>] references to connect related work and facilitate discovery.
  • Controlled access to stored items via explicit read/write operations (storeread, storewrite, storedelete) to maintain governance.

Quick Start

Store a decision with a concise summary and rationale, then retrieve it on demand using storeread.

Frequently Asked Questions about tool-store

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

FAQPage Schema
How do I persist architectural decisions and TODO contexts across multiple AI agent sessions?

Cross-referenced memory stores solve this by retaining architectural decisions and TODO contexts across sessions. They enable explicit storeread and storewrite operations to maintain provenance and durable project knowledge for multiple agents.

What is the best way to maintain provenance and auditability for architectural decisions?

To maintain provenance, use a durable memory store that enforces explicit loading, tagging, and link relationships. This controlled access preserves architectural decisions and TODO contexts for long-term auditability.

How do I store and retrieve architectural decisions with cross-references?

Store a decision with a concise summary and rationale, then retrieve it on demand using storeread. You can connect related work by applying proper tags and using [store:<id>] references to link relationships.

Can I use a cross-referenced memory store to manage TODO contexts for complex workflows?

Yes, a cross-referenced memory store supports complex workflows by operating across sessions and agents. It manages TODO contexts and architectural decisions through explicit read and write operations to maintain governance.

When do I need explicit read and write operations for project memory?

You need explicit read and write operations when managing complex workflows that require strict governance and auditability. Controlled access via storeread and storewrite ensures provenance is maintained for architectural decisions.