需求溯源：永远不丢「谁提的这功能」 Feature Request Tracker

这条用法在做什么What this use does

官方 Feature Request Tracker：从 Slack 和通话里挖需求，做成绑到具体客户的活清单，让规格书有真实需求轨迹。不建票、不承诺排期。 Official Feature Request Tracker: mines Slack and calls into a living list tied to customers, so the spec has a real demand trail. Does not file tickets or promise a schedule.

收录理由Why we listed it 官方 Product 新角色。现有客服退款/工单分拣不覆盖「需求溯源到客户」。 New official Product role. Support refunds / ticket triage do not cover a customer-tied demand trail.

上手路径How to start

1. 先跑一次安全范围Run a safe first pass

   先在可撤回、不外发的范围内试跑。本条未批准前：不新建工单、不承诺排期、不回复客户；只返回绑到客户的需求清单与出处。。 Try it first in a reversible, non-outbound scope. Until approved: Do not file tickets, promise a schedule, or reply to customers; return a customer-tied request list with sources only..

2. 存 SkillSave a Skill

   这条用法已包含可复用 Skill。跑通安全范围后，立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.

3. 再上 RoutineThen add a Routine

   输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.