laojin1900

365-chatgpt-pro-delivery

Coordinate one bounded collaboration between Codex and an explicitly requested ChatGPT Pro workspace. Use when the user asks Codex to consult ChatGPT Pro, obtain a Pro review, combine Pro research or creative work with Codex verification, or divide a named deliverable between the two, including an explicitly requested review of local work. Do not invoke for ordinary ChatGPT questions, local-only work that does not request Pro, or when the user forbids external transmission.

365-five-step-dev-claude

分级五步开发流程（业务型开发者版，Claude Code 版）。用户说「五步法」即为显式调用本技能；此外当用户提出任何开发需求——新功能、Bug 修复、页面改动、数据库/权限变更、接口、部署——也应触发。姊妹技能 365-five-step-retro-claude 负责本技能自身的运行复盘与迭代。

Code & Development Listed

365-five-step-dev-codex

The Codex edition of business-led five-step governance for scoped, risk-aware, evidence-verified delivery. Invoke explicitly when the user says 五步法, 365五步法, or 365五步法 Codex版, uses $365-five-step-dev-codex, or directly requests this Codex governance method. Invoke automatically only for an actual production or infrastructure change, a bulk or destructive live-data operation, an unresolved business permission or compliance decision, or a process-governance redesign. Do not invoke for requests that explicitly name the Claude edition. Do not invoke implicitly for ordinary features, database or migration-file authoring, permission implementation, commits, PRs, merges, local previews, deployment preparation, a dirty worktree by itself, general questions, or read-only analysis.

365-session-rotation-maintainer

Rotate, replace, or hand off a long-running Codex task to one successor while preserving durable work state, Git ownership, acknowledgement, and verified closeout. Use only when the user explicitly asks to rotate, replace, or hand off a Codex task or session to a successor. Do not invoke for archive-only task management, ordinary project cleanup, task age alone, generic health checks, or production execution.

discover-project-skills

Discover, inventory, summarize, audit, and extract reusable Agent Skills from the current repository. Use when users ask what skills a project has, want a project skill map, need to identify reusable workflows or domain knowledge, want to audit existing SKILL.md files, or ask to turn proven practices into portable skills. 中文：发现、盘点、总结、审计并提炼当前仓库中的可复用技能；当用户询问项目已有技能、需要项目技能地图、希望识别可复用流程或把成熟实践沉淀成标准技能时使用。

gws-weekly-digest

生成每周邮件+日程晨报/周报：用 gws CLI（或等效邮件/日历命令行）汇总上一周的邮件（总量、未读、重点发件人、疑似待回复）和本周（今日起七天）的日历日程，输出结构化中文或英文 markdown 晨报，并给出本周关注建议。当用户说「周报」「晨报」「每周邮件汇总」「周一晨报」「帮我汇总上周邮件和本周日程」「weekly digest」「Monday briefing」「weekly email+calendar summary」「邮件日程周报」时触发；也用于搭建此类定时摘要自动化。不用于：发送邮件、修改日历、实时邮件处理、非 Google 系的邮件/日历系统（Outlook/Exchange 需另行适配）。

gws-workspace

Operate Google Workspace — Gmail, Calendar, Drive, Sheets, Docs, Slides, Chat, Tasks — through the gws CLI (github.com/googleworkspace/cli) with read-by-default safety gates. Use when the user mentions gws, Gmail, email inbox/send/reply/triage, 邮件/收件箱/发邮件/未读邮件, Google Calendar, 日程/日历/创建会议, Google Drive, 谷歌网盘/上传 Drive, Google Sheets, 谷歌表格, Google Docs, 谷歌文档, or asks for Google Workspace automation such as daily/weekly mail+calendar digests (邮件汇总/日程周报). Also use when installing gws, configuring its OAuth client, or troubleshooting gws authentication errors.

Code & Development Listed

parallel-sessions-protocol

Coordinate any number of AI or human dev sessions working the same git repository in parallel — start-of-work registration (a draft PR is the shared board, with claim declarations), resource claiming (sequential numbers, file ownership), ledger-writes-only-at-merge-time, merge discipline (local merge preview, exclusive working directories, no `git add -A`), end-of-work registration (push-or-declare WIP, worktree cleanup, triggered write-backs), and a three-checkpoint awareness refresh. Use when multiple sessions / agents / worktrees develop one repo at the same time; when the user says 多会话并行, 并行轨道, 开工登记, 收工登记, 公告板, 会话撞车, 多个会话同时开发, coordinate parallel sessions, multiple Claude sessions on one repo, sessions keep colliding, track claims; when sequential resources (migration or decision numbers) or shared changelog/ledger docs keep colliding between branches; or when a session needs to know what other sessions are doing before acting. NOT for release/QA pipeline coordination through a dedicated controller lane,

Code & Development Listed

shopify-theme-delivery

Use when planning, building, migrating, validating, previewing, diagnosing, or releasing a Shopify Online Store 2.0 theme, including Liquid, JSON templates, sections, snippets, theme CSS or JavaScript, Theme Editor preservation, draft-theme writes, stale previews, dynamic DOM enhancements, or multi-page acceptance.