t-decision
Decide whether a feature should enter the t-tools workflow before tech research or PRD.
Profile →npx skills add timzaak/web-dev-skills --skill t-decision --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 产品立项决策 契约：`${CLAUDE_PLUGIN_ROOT}/protocols/decision-brief-contract.md` 跨阶段决策连续性：`${CLAUDE_PLUGIN_ROOT}/protocols/decision-continuity-contract.md` `/t-decision` 位于 `/t-tech-research` 和 `/t-prd` 之前，用来判断一个 feature 是否值得进入后续工程流程。它只做产品立项和范围取舍，不写 PRD、不做技术设计、不拆任务、不实现代码。 ## 输出 - `.ai/decision/<feature>.md` - `.ai/decision-log/<feature>.md` Markdown 使用 [template.md](${CLAUDE_PLUGIN_ROOT}/skills/t-decision
What does the t-decision skill do?
Decide whether a feature should enter the t-tools workflow before tech research or PRD.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-decision --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From timzaak/web-dev-skills, a repository with 55 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.