tdd

Generate and maintain technical design documents synchronized with implemented code.

1|Updated Mar 24, 2026

Search Tags:#tdd #architecture #linting #documentation #github #engineering

Ready to run

npx skills add https://github.com/EdgeApp/edge-dev-agents --skill tdd-edgeapp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/tdd
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill tdd-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, node, gh, and includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of documentation drift and incomplete design records by ensuring that technical design documents (TDDs) are always synchronized with the actual implemented code and verified through rigorous linting.

Core Features & Use Cases

Automated Verification: Uses a custom linting engine to ensure TDDs contain valid ToCs, anchor links, and no placeholder markers.
Living Documentation: Manages the lifecycle of design docs from gist-based drafts to committed repository files within PRs.
Use Case: After completing a complex feature implementation, use this skill to generate a design document that accurately reflects the final architecture, including sequence diagrams and decision alternatives, ensuring the documentation is as reliable as the code itself.

Quick Start

Ask the agent to write a technical design document for the current implementation and publish it to the repository.

Frequently Asked Questions about tdd

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

FAQPage Schema

How do I keep technical design documents synchronized with implemented code across multiple repositories?▼

Technical design documents can be synchronized with implemented code by generating and maintaining TDDs across multi-repo environments. This tracks design evolution, decision alternatives, and post-implementation retrospectives to prevent documentation drift.

What's the best way to automate verification of technical design documents for broken anchor links and placeholders?▼

Automating verification of technical design documents is done using a custom linting engine that ensures TDDs contain valid tables of contents, anchor links, and no placeholder markers before committing them to a repository.

Do I need GitHub CLI access to generate and publish design documents to a repository?▼

Yes, GitHub CLI access is required to generate and publish design documents. The process uses authenticated GitHub CLI access along with jq and node to perform linting, gist publication, and repository commits within pull requests.

Can I manage design document drafts as gists before committing them to a repository?▼

Yes, managing design document drafts as gists is supported. The documentation lifecycle flows from gist-based drafts to committed repository files included within pull requests, ensuring a living documentation process.

How does generating a technical design document after feature implementation improve architecture records?▼

Generating a technical design document after feature implementation accurately reflects the final architecture, including sequence diagrams and decision alternatives. This ensures the documentation remains as reliable as the codebase itself.

What are the limitations of using automated linting for technical design documents in multi-repo environments?▼

The automated linting for technical design documents in multi-repo environments is limited to checking ToCs, anchor links, and placeholder markers. It requires jq, node, and GitHub CLI dependencies to execute repository commits and gist publication.