pantsbang-yannik

Surveys the current repo's open GitHub issues, ranks them by triage label and dependency graph, and recommends an optimal execution order; when you pick one to start, it gates on whether the issue is clear enough to execute and routes unclear ones to the grill-with-docs skill before any code is written. It can also render the board as a self-contained HTML map that groups issues into business lines, draws their dependency arrows, and spells out which feature each chain ships once completed. Use WHENEVER the user asks what to work on next, which issue to pick up, to list / prioritize / sequence the backlog, for a dependency analysis, to visualize / draw / map the issues, their relationships, business lines, or what completing a chain unlocks, anything about *their own* issues ("my issues", who's blocking me, who's waiting on me, "我负责的 / 分给我的 / 谁在阻塞我 / 谁在等我"), "下一个做什么 / 排一下 issue 优先级 / 接下来推进哪个 / 这个 issue 能直接做吗 / 把 issue 关系和业务线画出来 / 生成依赖图 / 看板", or is about to start an issue and needs to know if it's ready — eve

基于「焦糖布丁理论」（Jobs-to-be-Done 任务理论）的文案升维引擎——把产品/功能从「产品维度」升到「用户真实任务维度」，找到不同维度的对手，产出整套官网与运营海报宣传文案。当用户想优化或重写官网/Landing Page 文案、提炼卖点与 slogan、写运营海报/营销文案、觉得现有文案太平/同质化/容易被竞品复制、想从用户真实需求(JTBD)角度重新定位产品，或直接点名「焦糖布丁理论 / 任务理论 / 顾客要的不是电钻是洞」时，都应使用本技能——即使用户只说「帮我把这些功能写成宣传语」「这个产品该怎么宣传」而没点名理论。