create-tech-design

create-tech-design is a skill for Claude Code, Codex from forthends/clockwork. It costs 0 tokens per session (798 once invoked), scanned A, original, MIT.

A procedure for turning a product requirements document into a technical design document. It covers the system structure, the interfaces between parts, the data entities, implementation tasks, and technical risks.

In plain words
What is it for?
Use it during a feature's technical-design stage after the requirements document is complete. It helps define APIs, data fields and constraints, module responsibilities, diagrams, risks, and estimated work.
Why use it?
It turns user needs and acceptance criteria into a concrete engineering plan before coding begins. This reduces gaps between what the product should do and how it will be built.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it during a feature's technical-design stage after the requirements document is complete. It helps define APIs, data fields and constraints, module responsibilities, diagrams, risks, and estimated work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/forthends/clockwork/create-tech-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add forthends/clockwork --skill create-tech-design
Clone the repo
git clone --depth 1 https://github.com/forthends/clockwork

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-tech-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/forthends/clockwork/create-tech-design/github.svg)](https://agentmods.dev/skills/forthends/clockwork/create-tech-design)
Your own site
<a href="https://agentmods.dev/skills/forthends/clockwork/create-tech-design"><img src="https://agentmods.dev/badge/skills/forthends/clockwork/create-tech-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-tech-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/forthends/clockwork/create-tech-design"><img src="https://agentmods.dev/badge/skills/forthends/clockwork/create-tech-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 798 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00798
Opus 5.5 $0.00000 $0.00319
Sonnet 5.5 $0.00000 $0.00160
Haiku 4.5 $0.00000 $0.00080

Measured 2mo ago against content hash cfdcf2d03a0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-tech-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/create-tech-design/SKILL.md · 89 lines

What it actually says

创建技术设计文档


技能信息

  • 技能名称:创建技术设计文档
  • 技能标识:create-tech-design
  • 一句话说明:基于 PRD 和模板,创建结构化的技术设计文档,涵盖架构、API 和数据模型
  • 适用角色:Developer

触发条件

当以下条件满足时,应调用本技能:

  • 工作流进入 tech_design 阶段
  • 需要将产品需求转化为技术实现方案

前置条件

调用本技能前,必须确保:

  1. requirements 阶段已完成(manifest.yaml 中 status 为 completed)
  2. PRD 文档 workflow/features/FEAT-<id>-<name>/prd.md 已存在且通过校验
  3. 已读取工作流定义了解 tech_design 阶段的输出要求

执行步骤

  1. 读取上游产物:读取 prd.md,逐条理解用户故事和验收标准
  2. 读取模板:读取 workflow/_templates/tech-design.md 获取文档结构
  3. 设计架构(architecture 章节):
    • 确定整体技术方案和架构选型
    • 绘制架构图,展示模块关系和数据流
    • 划分模块职责,说明技术选型理由
    • 记录关键设计决策及备选方案对比
  4. 设计 API(api_design 章节):
    • 为每个功能点定义 API 接口
    • 包含:方法、路径、参数、请求体、响应体、错误码
    • 确保接口设计覆盖 PRD 中所有用户故事
  5. 设计数据模型(data_model 章节):
    • 定义数据实体及字段
    • 标注字段类型、约束和索引
    • 绘制实体关系图
  6. 规划实现:
    • 拆分实现任务并预估工时
    • 识别技术风险和缓解措施
  7. 保存文件:将完成的技术设计保存到 workflow/features/FEAT-<id>-<name>/tech-design.md

输入

输入 来源 说明
PRD 文档 workflow/features/FEAT-<id>-<name>/prd.md 产品需求和验收标准
技术设计模板 workflow/_templates/tech-design.md 文档结构模板
工作流定义 workflow/_definitions/feature.yaml 了解 validation 校验规则

输出

输出 路径 说明
技术设计文档 workflow/features/FEAT-<id>-<name>/tech-design.md 完整的技术设计方案

质量检查

完成技术设计后,对照以下清单自检:

  • architecture 章节是否包含方案说明和架构图
  • 每个设计决策是否说明了选择理由
  • api_design 是否覆盖了 PRD 中的所有功能点
  • 每个 API 接口是否包含完整的请求/响应定义
  • data_model 是否包含所有实体和字段说明
  • 实体间关系是否清晰
  • 技术风险是否已识别
  • 对 PRD 中有疑问的部分是否标注了 [待确认]

完成自检后,调用 validate-artifact 技能进行正式校验。

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 89 lines · 0 tokens per session scan A cfdcf2d03a0e

Subscribe to this mod's changes

create-tech-design is a skill published in the GitHub repository forthends/clockwork (8 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 798 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens