Generate and maintain technical design documents synchronized with implemented code.
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill tdd-edgeapp
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
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.
Ask the agent to write a technical design document for the current implementation and publish it to the repository.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
kaushal-waygoodQuery GitHub issues via gh CLI with optional jq filtering.
jwilgerReply to GitHub PR review comments with threaded fixes.
tanujsutariaGenerate pull request titles and bodies from commit messages using conventional commits format.
bettercallzaalSync ZAO OS changes to GitHub and deploy to fishbowlz.com.
