Plan and run AI-agent dynamic workflows for complex tasks that benefit from explicit orchestration, goal mode, subagents or simulated work packets, approval gates, integration, verification, and reusable workflow artifacts. Use when the user invokes this skill, asks for a swarm, subagents, parallel agents, a dynamic workflow, a large migration or audit, multi-track research plus implementation, or Claude Code-style workflow orchestration.
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask 设计/做页面/做组件/UI/前端/截图 or say a screen is ugly, unclear, inconsistent, or visually wrong. Not for backend logic or data pipelines.
Act as a warm, incisive Stanford d.school style life designer for multi-turn personal life design conversations in Chinese. Use when the user asks for 人生设计, 斯坦福人生设计课, 奥德赛计划, 工作观/人生观梳理, 心流和能量地图, 重力问题判断, 个人五年版本, or wants a reusable life-design interview that ends in a detailed personal life design blueprint. Do not use for ordinary career tests, one-off advice, or clinical mental-health support.
季度开发工作总结 skill。用于一站式只读采集 GitHub 开发活动和飞书协作证据，并生成面向老板/领导层可扫读的本地 HTML 总面板和 summary.json。包含 GitHub 模块、飞书模块和价值总览模块：GitHub 统计 commit、PR、issue、review、仓库、上季度环比、贡献画像、功能类 PR/修复类 PR 归类、PR 变更审计、项目组合、新建仓库、新启动项目、重点工作线索、项目价值归因和重点项目证据展开；飞书统计文档发现/内容读取、消息搜索、日历日程和权限缺口；总面板展示代码/PR 证据 -> 功能类/修复类 PR -> 项目结果 -> 价值主线的可追溯映射。默认不写入 GitHub 或飞书，不创建/修改/发送任何外部对象。
Reviews completed changes, code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask review/看看代码/检查一下/合并前/看看issue/PR/release/push or to implement an approved plan, with functional acceptance, dynamic risk modeling, adversarial review, and safety gates for dirty and untracked worktrees. Not for exploring ideas, debugging root causes, or prose review.
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users ask 排查/报错/崩溃/不工作/回归/判断为什么报错, or say something used to work and now fails. Not for code review or new features.
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask 出方案/给方案/深入分析/怎么设计/有没有必要/值不值得/plan this/how should I/should we keep this for features, architecture, or value judgments. Not for bug fixes or small edits.
Create pull requests with repository templates, explicit GitHub base/head resolution, and fork/upstream safety. Use when asked to create a PR, especially across forks where the PR head must stay owner-qualified and must not silently fall back to an upstream same-name branch.