relay-doc

Draft and save implementation documents to the Data Relay docs directory after approval.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/numeric-io/the-data-relay --skill relay-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-doc
Source: https://github.com/numeric-io/the-data-relay/tree/main/skills/relay-doc
Command: npx skills add https://github.com/numeric-io/the-data-relay --skill relay-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This command automates the careful capture and archival of implementation documents (plans, specs, architectures) produced during conversations, ensuring decisions and designs are preserved with explicit oversight.

Core Features & Use Cases

  • Guides users to draft and preserve planning, architecture, and specification documents in the Data Relay docs directory.
  • Enforces an explicit approval step from March before writing, reducing accidental commits and improving governance.

Quick Start

Draft the document content based on the current conversation, present it to March for explicit approval, and only then write to <vault>/local/docs/ using the doc template.

Frequently Asked Questions about relay-doc

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

FAQPage Schema
How do I save implementation documents with an explicit approval step?

To save implementation documents with an explicit approval step, the content is drafted from the conversation, presented for confirmation, and only written to the docs directory after approval is granted. This process ensures governance and traceability for plans and specs.

What is the best way to preserve architecture notes and specs in a knowledge management vault?

The best way to preserve architecture notes in a knowledge management vault is to draft the content and write it using a standardized doc template with a YAML header, ensuring the design decisions are archived with explicit oversight and traceability.

How does the governance approval process work for doc-writing drafts?

The governance approval process for doc-writing drafts requires presenting the drafted content to obtain explicit confirmation before writing. This prevents accidental commits and ensures only approved specifications are archived in the directory.

Can I write planning documents to the docs directory without explicit confirmation?

No, writing planning documents to the docs directory requires explicit confirmation. Drafting the content must be followed by an explicit approval step to maintain governance and reduce accidental commits before the file is saved.

Do I need a specific template to save specs and architecture notes?

Yes, saving specs and architecture notes requires using a standardized doc template with a YAML header. This ensures the preserved implementation documents maintain consistent structure and traceability within the knowledge management directory.