Testing Skills With Subagents
ed3dai/ed3d-plugins
A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown…
Install Product Feature Tech Implement
$ npx skills add digoal/blog --skill product-feature-tech-implement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install digoal/blog product-feature-tech-implement --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/digoal/blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-feature-tech-implement .claude/skills/product-feature-tech-implement && 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 "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .claude/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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/digoal/blog/tree/master/skills/product-feature-tech-implementType 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 digoal/blog --skill product-feature-tech-implement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install digoal/blog product-feature-tech-implement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product-feature-tech-implement .agents/skills/product-feature-tech-implement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .agents/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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 digoal/blog --skill product-feature-tech-implement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install digoal/blog product-feature-tech-implement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product-feature-tech-implement .cursor/skills/product-feature-tech-implement && 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 "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .cursor/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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/digoal/blog.git --path skills/product-feature-tech-implement--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 digoal/blog --skill product-feature-tech-implement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install digoal/blog product-feature-tech-implement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product-feature-tech-implement .gemini/skills/product-feature-tech-implement && 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 "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .gemini/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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 digoal/blog product-feature-tech-implementInstalls 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 digoal/blog --skill product-feature-tech-implement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product-feature-tech-implement .github/skills/product-feature-tech-implement && 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 "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .github/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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 digoal/blog --skill product-feature-tech-implement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install digoal/blog product-feature-tech-implement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digoal/blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product-feature-tech-implement .opencode/skills/product-feature-tech-implement && 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 "product-feature-tech-implement" agent skill from https://github.com/digoal/blog/tree/master/skills/product-feature-tech-implement into .opencode/skills/product-feature-tech-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-feature-tech-implement", 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.
Facts
- Skill name
product-feature-tech-implement- GitHub stars
- 8.6k
- Token cost
- ~1k tokens
- SKILL.md length
- 299 words
- Files
- 6 (incl. references)
- Skills in repo
- 98
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown…
- Works in 3 steps: 测试者看不到代码。这是与 product-feature-tech-design… → 循环 A 必须有终止条件。评审通过才能退出循环… → 三方各持独立 prompt。下方 references 里固化的…
- Tasks that involve Test-driven development
- SKILL.md covers 核心约束(决定一切), 输入, 角色契约 and 编排流程, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Product Feature Tech Implement is an agent skill from digoal/blog. 基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown 总结报告到当前项目的 markdown/ 目录。适用于:实施功能设计文档、按设计稿开发并自验证、闭环式开发流程、PostgreSQL 插件/扩展开发、需要 build + 部署 + 跑测的工程项目、TDD 式实施循环。
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/developer-prompt.md` and `references/reviewer-prompt.md`).
It sits in Testing & QA, covering Test-driven development and Subagents. It works with PostgreSQL. The repository describes itself as: AI,Opensource,Database,Business,Finance,Minds. git clone --depth 1 https://github.com/digoal/blog. The licence is GPL-2.0.
When your agent uses it
- Tasks that involve Test-driven development
- Tasks that involve Subagents
Example prompts
- “/product-feature-tech-implement”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- 测试者看不到代码。这是与 product-feature-tech-design 一脉相承的隔离原则 — 测试者只读设计文档,绝不能读开发者写的代码、commit message 中的代码 diff、或评审意见里贴的代码片段。
- 循环 A 必须有终止条件。评审通过才能退出循环 A;测试通过(且已有测试不退化)才能结束任务。
- 三方各持独立 prompt。下方 references 里固化的 subagent prompt 是隔离的物理边界,不要在主对话里临场改写。
What it can do on your machine
Read from SKILL.md and the folder at commit 69fb793. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Feature Tech Implement loads about 1k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 299 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from digoal/blog at commit 69fb793, republished under its GPL-2.0 licence (© digoal). 299 words, ~1,017 tokens.
Download SKILL.mdSave it as
.claude/skills/product-feature-tech-implement/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- product-feature-tech-implement
- description
- 基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown 总结报告到当前项目的 `markdown/` 目录。适用于:实施功能设计文档、按设计稿开发并自验证、闭环式开发流程、PostgreSQL 插件/扩展开发、需要 build + 部署 + 跑测的工程项目、TDD 式实施循环。
Product Feature Tech Implement
核心约束(决定一切)
- 测试者看不到代码。这是与
product-feature-tech-design一脉相承的隔离原则 — 测试者只读设计文档,绝不能读开发者写的代码、commit message 中的代码 diff、或评审意见里贴的代码片段。 - 循环 A 必须有终止条件。评审通过才能退出循环 A;测试通过(且已有测试不退化)才能结束任务。
- 三方各持独立 prompt。下方 references 里固化的 subagent prompt 是隔离的物理边界,不要在主对话里临场改写。
输入
| 输入 | 必填 | 用途 |
|---|---|---|
| 功能设计文档路径 | 是 | 所有角色的唯一共同依据 |
| 源码目录路径 | 是 | 开发者写入、评审者读取、测试者不读 |
| 已有测试目录 | 是 | 测试者运行回归 |
| 测试环境信息 | 否(按需) | 例如:PG 源码路径、PG 实例初始化命令、插件加载方式、构建系统(Make/CMake/Cargo/...) |
| 增量代码范围 | 是(从第 2 轮起) | 仅给评审者,标识本次新增/修改的文件 |
| 上轮评审意见 | 否(从第 2 轮起) | 给开发者修复用 |
| 上轮测试报告 | 否(从第 2 轮起) | 给开发者修复用 |
如果输入不全,先停下来问用户补齐,不要凭空白开始。
角色契约
角色 1:开发者(Subagent 1)
| 项 | 约束 |
|---|---|
| 输入 | 设计文档 + 上轮 review 意见(若有) + 上轮测试报告(若有) + 源码目录 |
| 输出 | 增量代码(diff 或文件列表)+ 开发者自检说明 |
| 可以看 | 设计文档全部、源码目录全部、已有测试目录的文件名(不是内容)、build/部署/运行日志 |
| 不可以看 | 测试者写的测试代码 |
| 隔离实现 | 由 references/developer-prompt.md 物理屏蔽 |
角色 2:评审者(Subagent 2)
| 项 | 约束 |
|---|---|
| 输入 | 设计文档 + 增量代码(本轮新增/修改的文件)+ 上一轮 review 报告(若有) |
| 输出 | review 报告(通过 / 不通过 + 问题清单 + 严重度) |
| 可以看 | 设计文档全部、增量代码 |
| 不可以看 | 测试代码、上轮测试报告(避免被「能跑通」污染 review 视角) |
| 通过条件 | 所有 P0 问题已修复,无新增 P0/P1 问题 |
角色 3:测试者(Subagent 3)
| 项 | 约束 |
|---|---|
| 输入 | 仅功能设计文档 + 已有测试目录路径(运行用,不是阅读用) + 测试环境信息 |
| 输出 | 测试报告(新增测试用例 + 执行结果 + 已有测试执行结果) |
| 可以看 | 设计文档全部、运行 build/部署/跑测的命令、命令输出 |
| 绝对不可以看 | 开发者写的源码、commit message 中的 diff、review 报告里贴的代码片段 |
| 隔离实现 | 由 references/tester-prompt.md 强红线 |
编排流程
[读取输入]
↓
loop A:
① 启动 subagent 1(开发者)
- 首轮:基于设计文档实现
- 后续轮:基于设计文档 + review 意见 + 测试报告修复
② 启动 subagent 2(评审者)
- 基于设计文档 + 本轮增量代码 review
③ review 通过?
- 否 → 回到 loop A 开始(开发者按 review 修)
- 是 → 退出 loop A
④ 启动 subagent 3(测试者)
- 基于设计文档写新增测试 + 跑全量测试
⑤ 测试通过?
- 否 → 回到 loop A 开始(开发者按 review + 测试报告修)
- 是 → 退出整体流程
⑥ 关闭三个 subagent
⑦ 生成总结报告循环退出判定
loop A 退出(进入测试):
- review 报告明确写
verdict: pass - 没有任何 P0/P1 残留
整体流程退出:
- review pass 且 测试报告
verdict: pass - 测试报告必须包含:新增测试用例数、通过/失败/跳过统计、已有测试全部通过(无退化)
- 性能/安全/兼容性的"必测项"覆盖
防死循环:
- 同一 review 意见反复未修复 3 轮 → 暂停,询问用户是否调整设计文档
- 同一测试用例反复失败 3 轮 → 暂停,询问用户是设计问题还是实现问题
subagent 启动规范
每次启动 subagent 时,必须:
- 加载对应的 references 模板作为 subagent 的角色契约
- 在 prompt 开头显式告知 subagent:
- 它是什么角色
- 它能读什么、不能读什么
- 它的输入路径(设计文档、上轮报告等)
- 它的输出格式
- 显式约束:不要让 subagent 之间互看对方的产出
- subagent 完成后,只把它的最终输出带回主对话,不要把它的内部 reasoning 全量带回
详细 prompt 见:
references/developer-prompt.mdreferences/reviewer-prompt.mdreferences/tester-prompt.md
报告文件位置
| 报告 | 路径 | 说明 |
|---|---|---|
| Review 报告 | markdown/<topic>-review-<round>-<YYYYMMDD>.md | 每轮 1 份 |
| 测试报告 | markdown/<topic>-test-<round>-<YYYYMMDD>.md | 每轮 1 份 |
| 总结报告 | markdown/<topic>-implement-summary-<YYYYMMDD>.md | 最终 1 份 |
<topic> 与功能设计文档保持一致。
总结报告(见 references/summary-template.md)
至少包含:
- 任务概览(设计文档 + 源码目录 + 测试环境)
- 实施时间线(每轮做了什么、review 结论、测试结论)
- 最终增量代码清单(文件级)
- 最终测试覆盖(新增用例数、已有用例回归结果)
- 遗留风险与后续建议
- 关键决策记录(为什么这么做)
质检清单(交付前自检)
- 测试者 subagent 启动时 prompt 中显式写了"绝对不能看代码目录"
- 每轮 review 报告有明确的 verdict(pass / fail + 原因)
- 每轮测试报告有明确的 verdict(pass / fail + 失败用例)
- 已有测试无退化(失败数 0 或与基线一致)
- 总结报告保存到
markdown/目录 - 三个 subagent 已被关闭(没有遗留子任务)
- 流程中没有把开发者代码泄漏给测试者
- 防死循环保护(同问题 3 轮未解决)未触发 / 已与用户确认
参考资料
references/developer-prompt.md— 开发者 subagent 角色契约references/reviewer-prompt.md— 评审者 subagent 角色契约references/tester-prompt.md— 测试者 subagent 角色契约(强隔离)references/summary-template.md— 总结报告模板
上下游 skill
- 上游:
product-feature-tech-design— 输入是它的产物(功能设计文档) - 本 skill — 实施 + review + test 闭环
- 下游:无需,本 skill 是交付终点
© digoal, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/product-feature-tech-implement of digoal/blog.
- SKILL.md
- agents/openai.yaml
- references/developer-prompt.md
- references/reviewer-prompt.md
- references/summary-template.md
- references/tester-prompt.md
Open the folder on GitHubat commit 69fb793
Compare with similar skills
Product Feature Tech Implement 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 |
|---|---|---|---|---|---|---|
| Product Feature Tech Implement this skilldigoal/blog | 8.6k | — | ~1k | Automated safety check: Pass | GPL-2.0 | |
| Testing Skills With Subagentsed3dai/ed3d-plugins | 250 | 3 repos | ~3.5k | Automated safety check: Pass | None | |
| Nv Implementnovuhq/novu | 40k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Test PromptNeoLabHQ/context-engineering-kit | 1.7k | — | ~5k | Automated safety check: Pass | GPL-3.0 | |
| Tapd Story ImplementTencentBlueKing/bk-bcs | 840 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Implementopen-octo/octo-agent | 125 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Nv Implement
novuhq/novu
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.
Test Prompt
NeoLabHQ/context-engineering-kit
A skill your agent uses when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt…
Tapd Story Implement
TencentBlueKing/bk-bcs
迭代执行流水线代码实现阶段。基于 tasks.md 调用 /speckit.implement 以 TDD 模式完成全部任务。
Implement
open-octo/octo-agent
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a…
Create Skill
NeoLabHQ/context-engineering-kit
Guide for creating effective skills. An agent skill from NeoLabHQ/context-engineering-kit.
More from digoal/blog
All 98 skills in this repoArticle Fact Checker
digoal/blog
三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…
Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
Digoal
digoal/blog
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation…
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Product Multi Role Analysis
digoal/blog
Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles…
Blog Cover Poster
digoal/blog
Turn a blog post, article, notes, or any source material into a set of vertical poster images — one cover plus several coherent content slides that explain the core points.
Related
Works with
Categories
Questions about Product Feature Tech Implement
What does Product Feature Tech Implement do?
基于功能设计文档(由 product-feature-tech-design 产出或等价输入)、源码目录、以及测试所依赖的环境信息(例如 PostgreSQL 插件开发需要的 PG 源码/实例、第三方依赖),编排「开发者 ↔ 评审者 ↔ 测试者」三方隔离的实施循环,直至评审通过、且所有测试(新增 + 已有)通过。三方互不可见,测试者绝对不能看到开发者写的代码。完成后输出 markdown…. Product Feature Tech Implement is an agent skill from digoal/blog.
When should I use Product Feature Tech Implement?
Product Feature Tech Implement fits situations like: tasks that involve Test-driven development; tasks that involve Subagents.
How do I install Product Feature Tech Implement in Claude Code?
Run `npx skills add digoal/blog --skill product-feature-tech-implement -a claude-code`. Or copy the skill folder (skills/product-feature-tech-implement in digoal/blog) into .claude/skills/product-feature-tech-implement in your project. Claude Code loads it when a task matches its description.
How do I install Product Feature Tech Implement in Codex?
Run `npx skills add digoal/blog --skill product-feature-tech-implement -a codex`. Or copy the skill folder (skills/product-feature-tech-implement in digoal/blog) into .agents/skills/product-feature-tech-implement in your project. Codex loads it when a task matches its description.
Can I use Product Feature Tech Implement in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add digoal/blog --skill product-feature-tech-implement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-feature-tech-implement, .gemini/skills/product-feature-tech-implement, .github/skills/product-feature-tech-implement and .opencode/skills/product-feature-tech-implement in your project.
What does Product Feature Tech Implement need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Feature Tech Implement is instructions for the agent only.
Does Product Feature Tech Implement access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Product Feature Tech Implement safe to install?
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.
What licence does Product Feature Tech Implement use?
Product Feature Tech Implement is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Product Feature Tech Implement use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.
What are the alternatives to Product Feature Tech Implement?
Skills that share tags, products or a category with Product Feature Tech Implement: Testing Skills With Subagents (ed3dai/ed3d-plugins, 250 stars), Nv Implement (novuhq/novu, 40k stars), Test Prompt (NeoLabHQ/context-engineering-kit, 1.7k stars) and Tapd Story Implement (TencentBlueKing/bk-bcs, 840 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Feature Tech Implement?
digoal (a GitHub user) maintains it in digoal/blog, which has 8,587 GitHub stars. The repository holds 98 skills in this directory. The repository was last updated on September 28, 2026.
Source: digoal/blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.