duck
By-hand trigger only. When the user types /duck, explain the current topic / latest answer to a cute CEO non-coder duck. Do not auto-trigger.
- License 许可
- MIT
- 最近更新
- 2026-05-20
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- duck
- description
- By-hand trigger only. When the user types /duck, explain the current topic / latest answer to a cute CEO non-coder duck. Do not auto-trigger.
03 SKILL.md 正文
Explain to a cute ceo non coder duck please.
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
reverification
By-hand only — DO NOT auto-trigger. When the user types /reverification (or asks for "reverify this", "independent verification", "LLM-uncheatable check", "第三方再验证", "用 repo 之外的方法验证"), re-verify recently-completed work using verification methods that **existed before this repo existed** and that an LLM agent cannot fabricate. Pick 3-5 verifications from a 10-family menu (hardware / cryptographic / blockchain / external real-system / mathematical / temporal / content authenticity / physical / network / third-party trust), dispatch them via real tools that capture raw evidence, and report PASS / FAIL / INCONCLUSIVE based ONLY on captured evidence — never on internal reasoning. Refuse to fall back on TeamBrain's bespoke verifiers (judge harness, fastprobe, /review, feature-verification gates) because those did NOT exist before the repo.
repo-issues-status
TeamBrain 仓库**全量 issue 全景**报告(all-scope only)。仅当用户问"status of all issues" / "show me all issues" / "what issues are open" / "all open issues" / "issue 状态(全景)" / "所有 issue 状态" / "issue 全景" / "仓库 issue 概览" / "还有哪些 open issue" 这类**仓库级、多 issue、概览类**问题时触发。**不要在以下情况触发**:(a) 用户问单个 issue 的状态("what's the status of issue