Development Workflow
runceel/ReactiveProperty
ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery.
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .claude/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .claude/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-docType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .agents/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .agents/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .cursor/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .cursor/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tech-leads-club/agent-skills.git --path 'packages/skills-catalog/skills/(creation)/create-technical-design-doc'--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .gemini/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .gemini/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creatorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .github/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .github/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tech-leads-club/agent-skills technical-design-doc-creator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tech-leads-club/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'packages/skills-catalog/skills/(creation)/create-technical-design-doc' .opencode/skills/technical-design-doc-creator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-design-doc-creator" agent skill from https://github.com/tech-leads-club/agent-skills/tree/main/packages/skills-catalog/skills/(creation)/create-technical-design-doc into .opencode/skills/technical-design-doc-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-design-doc-creator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
technical-design-doc-creatorCreates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery.
Technical Design Doc Creator is an agent skill from tech-leads-club/agent-skills. Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Use when user asks to "write a design doc", "create a TDD", "technical spec", "architecture document", "RFC", "design proposal", or needs to document a technical decision before implementation. Do NOT use for README files, API docs, or general documentation (use docs-writer instead).
Its SKILL.md is about 13k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Development, covering Architecture decision records, Technical documentation and Test-driven development. The repository describes itself as: The secure, validated skill registry for professional AI coding agents. Extend Antigravity, Claude Code, Cursor, Copilot and more with absolute confidence.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6df68d5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
nxkubectlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.launchdarkly.comAlso links to:
google.github.iosre.googleowasp.orgadr.github.ioFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_KEYSTRIPE_SECRET_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Technical Design Doc Creator loads about 13k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 1,996 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,996 words (~12,915 tokens).
“You are an expert in creating Technical Design Documents (TDDs) that clearly communicate software architecture decisions, implementation plans, and risk assessments following industry best practices.”
SKILL.md and 1 other file in packages/skills-catalog/skills/(creation)/create-technical-design-doc of tech-leads-club/agent-skills.
Open the folder on GitHubat commit 6df68d5
Technical Design Doc Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Design Doc Creator this skilltech-leads-club/agent-skills | 7k | — | ~13k | Automated safety check: Pass | Custom licence | |
| Development Workflowrunceel/ReactiveProperty | 944 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Docsbrickbots/PiFinder | 250 | — | ~6.2k | Automated safety check: Pass | GPL-3.0 | |
| Evidence-Backed Documentation Writerbgauryy/octocode | 949 | — | ~2k | Automated safety check: Pass | MIT | |
| Write Vibe ADRmistralai/mistral-vibe | 5.1k | — | ~942 | Automated safety check: Pass | Apache-2.0 | |
| Technical Documentation Templatesbybren-llc/safe-agentic-workflow | 423 | — | ~1.2k | Automated safety check: Pass | MIT |
runceel/ReactiveProperty
ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.
brickbots/PiFinder
Author and edit PiFinder's user-facing documentation in the project's house style.
bgauryy/octocode
Writes, repairs and copyedits project docs against the Google developer documentation style guide, verifying claims in the repository before stating them.
mistralai/mistral-vibe
Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.
bybren-llc/safe-agentic-workflow
Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
tech-leads-club/agent-skills
Creates, validates and renders Mermaid diagrams to SVG, PNG or ASCII, including C4 and AWS architecture-beta, flowcharts, sequence diagrams and ERDs.
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
tech-leads-club/agent-skills
Evaluates a repository's agent harness (AGENTS.md, rules, skills) for broken paths, redundant instructions and usefulness, and stops at reports.
tech-leads-club/agent-skills
Designs scalable NestJS modular monoliths with domain-driven design, Clean Architecture layers and optional CQRS, defining bounded contexts and strict module boundaries.
Categories
Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery. Technical Design Doc Creator is an agent skill from tech-leads-club/agent-skills. Creates comprehensive Technical Design Documents (TDD) with mandatory and optional sections through interactive discovery.
Technical Design Doc Creator fits situations like: user asks to write a design doc; architecture document; design proposal; needs to document a technical decision before implementation.
Run `npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a claude-code`. Or copy the skill folder (packages/skills-catalog/skills/(creation)/create-technical-design-doc in tech-leads-club/agent-skills) into .claude/skills/technical-design-doc-creator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a codex`. Or copy the skill folder (packages/skills-catalog/skills/(creation)/create-technical-design-doc in tech-leads-club/agent-skills) into .agents/skills/technical-design-doc-creator in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tech-leads-club/agent-skills --skill technical-design-doc-creator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-design-doc-creator, .gemini/skills/technical-design-doc-creator, .github/skills/technical-design-doc-creator and .opencode/skills/technical-design-doc-creator in your project.
Going by SKILL.md and its folder, Technical Design Doc Creator needs the command-line tools its instructions call (nx and kubectl) and credentials named API_KEY and STRIPE_SECRET_KEY. Our summary lists: A credential in API_KEY.
SKILL.md names 5 domains. In commands or code: api.launchdarkly.com; the agent is likely to contact it when it follows the instructions. As links in the text: google.github.io, sre.google, owasp.org and adr.github.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Technical Design Doc Creator has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 13k tokens (SKILL.md is roughly 52k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Technical Design Doc Creator: Development Workflow (runceel/ReactiveProperty, 944 stars), Docs (brickbots/PiFinder, 250 stars), Evidence-Backed Documentation Writer (bgauryy/octocode, 949 stars) and Write Vibe ADR (mistralai/mistral-vibe, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
tech-leads-club (a GitHub organization) maintains it in tech-leads-club/agent-skills, which has 7,045 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 9, 2026.
Source: tech-leads-club/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.