relay-impl

Generate a concrete implementation plan with file paths and signatures for approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between a conversational spec and a concrete, code-level implementation plan, ensuring an explicit approval gate before any file writes to the vault.

Core Features & Use Cases

  • Generates precise, file-path level implementation plans from a discussion.
  • Enforces an approval workflow before writing to local/impls/.
  • Uses templates to standardize plan metadata and cross-linking with project notes.

Quick Start

Draft the implementation plan based on the current conversation and present for approval before writing to the vault.

Frequently Asked Questions about relay-impl

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

FAQPage Schema
How do I generate an implementation plan from a specification without writing code yet?

You can generate a concrete implementation plan directly from your conversational spec, capturing exact file paths, function signatures, and type definitions. This ensures a structured approval gate before any code is written to the vault.

What is an implementation plan with an approval gate?

An implementation plan with an approval gate is a concrete, code-level plan generated from a discussion that requires explicit user approval before writing to local implementation directories. It bridges the gap between conversational specs and actual file writes.

How do I turn a conversational spec into file-path level implementation details?

To turn a conversational spec into file-path level implementation details, use templates to standardize metadata and cross-link project notes. The output includes exact file paths, function signatures, type definitions, and wiring details ready for implementation.

Do I need to approve the implementation plan before it writes to the vault?

Yes, you need to approve the implementation plan before it writes to the vault. The system presents a drafted plan based on the current conversation and enforces an explicit approval workflow before writing any files to local implementation directories.

What should be included in a concrete implementation plan for code generation?

A concrete implementation plan for code generation should include exact file paths, function signatures, type definitions, and wiring details. It must also contain a frontmatter block, an intended destination path, and references to project context and templates.

Can I use templates to standardize implementation plan metadata and cross-linking?

Yes, you can use templates to standardize implementation plan metadata and cross-linking with project notes. This ensures the generated plan remains self-contained, consistent, and ready for immediate implementation within your established project structure.