WeWrite 选题模块：抓取全网热点 + 垂类高频需求 + 历史表现分析 + 搜索需求，为公众号 生成 10 个评分排序的选题（含高频角度与常青选题）。 触发关键词：公众号选题、找几个选题、今天写什么、热点选题、热搜选题、爆款选题、选题建议。 需要公众号/微信上下文；不应被抖音/短视频/网站的选题需求触发。

WeWrite 风格设置模块：首次使用引导（onboard）+ 重设公众号写作风格配置（style.yaml）。 触发关键词：重新设置风格、修改风格配置、设置公众号风格、公众号首次设置、换写作人格、 改排版主题偏好。也由主入口 wewrite 在缺 style.yaml 时自动激活。 不应被通用的"改文风"、"润色"触发——那是编辑动作，不是配置动作。

WeWrite 数据复盘模块：拉取微信公众号文章的阅读/分享/点赞数据，回填历史记录并给出 选题、标题、框架的调整建议。 触发关键词：看看文章数据、文章数据怎么样、效果复盘、看看表现、阅读量怎么样。 需要公众号/WeWrite 上下文；不应被通用的"数据分析"触发。

微信公众号内容主入口：完成选题、素材、写作和审稿，并按用户要求独立追加配图、排版或草稿箱发布。 也负责把风格设置、学习修改、数据复盘和多平台改写分发给对应 wewrite-* 模块。 触发关键词：公众号、微信文章、微信推文、草稿箱、微信排版、写公众号、写一篇。 通用文章、博客、邮件、短视频和网站 SEO 不触发。

WeWrite 多平台改写模块：把一篇公众号文章（或指定源稿）内容级真改写成其他平台版本， 当前支持小红书（图文笔记）、抖音（口播脚本），检查编辑质量与源稿相似度。 触发关键词：改写成小红书、小红书版、抖音版、口播稿、多平台分发、一稿多发、平台改写。 不应被"翻译"、"缩写"、"换个标题"触发——那些是单平台编辑动作。

WeWrite 编辑审稿模块：核对任务、事实来源、观点和实用性，必要时直接改稿，只有通过编辑门槛 才生成公众号成稿。也响应“检查这篇文章”。通用代码 review 和网站 SEO 不触发。

WeWrite 排版发布模块：把 Markdown 做成微信预览，或在用户明确授权后推入公众号草稿箱； 也支持主题画廊和图片帖。只处理微信公众号。

WeWrite 自学习模块：从用户的人工修改中学习写作偏好（playbook 飞轮）、导入范文建风格库、 从公众号文章学习排版主题。 触发关键词：学习我的修改、我改了学习一下、导入范文、学习这篇文章、查看范文库、 学习排版、学排版。 不应被通用的"学习"、"总结这篇文章"触发——需要公众号/WeWrite 上下文。

Long-running task loop using /loop (Claude Code dynamic mode) and ScheduleWakeup to re-enter with fresh context on each wake-up. Internally invokes harness-work through Agent. Trigger: long-running, loop, wake-up, autonomous. Do NOT load for: one-shot task execution, review, release, planning.

Manage SSOT, memory, and cross-tool memory search. Guardian of decisions.md and patterns.md. Use when user mentions memory, SSOT, decisions.md, patterns.md, merging, migration, SSOT promotion, sync memory, save learnings, memory search, harness-mem, past decisions, or record this. Do NOT load for: implementation work, reviews, ad-hoc notes, or in-session logging.

File cleanup and archiving. Tidies up bloated Plans.md, session-log.md, old logs, and state files. Trigger: /maintenance, cleanup, archive, organize, split session-log. Do NOT load for: implementation, review, release, new feature development.

HAR: Sync Plans.md with implementation. Drift detect, marker update, retrospective. Trigger: sync-status, where am I, check progress. --snapshot for snapshots. Do NOT load for: planning, implementation, review, release.

HAR: Multi-angle code, plan, scope review. Security/quality check. Trigger: review, code review, plan review, scope analysis. Do NOT load for: implementation, new features, bugfix, setup, release.

Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP / cc:TODO / cc:完了 counts, percentage, elapsed/estimated minutes, cost so far/estimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.

HAR: Research-backed, team-validated task planning, Plans.md management, progress sync. Trigger: create a plan, add tasks, update Plans.md, mark complete, check progress. Do NOT load for: implementation, review, release.

Generate a Plan Brief HTML for non-engineer vibecoders before implementation starts. Searches harness-mem (project-only) for relevant past decisions, patterns, and Plans archive entries, then renders a single-file HTML artifact summarizing understanding, options, risks, acceptance criteria, and confidence. Use when the user requests a planning preview, a non-engineer-friendly summary before approval, or says: plan brief, planning preview, 計画概要, 計画レビュー. Do NOT load for: actual implementation, code review, release work.

HAR: Codex-native long-running loop runner. Uses a real background runner that executes one ready batch per cycle through Breezing by default, with status/stop controls. Trigger: long-running, loop, autonomous, background, Codex. Do NOT load for: one-shot implementation, normal review, release.

Generate an Acceptance Demo HTML for non-engineer vibecoders right before ship/wait/reject decision. Reads back the acceptance_criteria that were stored as personal-preference.v1 by harness-plan-brief (joined by user_request_hash), then renders a single-file HTML showing each criterion as verified or unverified along with a ship/wait/reject recommendation. Use when the user asks for an acceptance review, wants to decide whether to ship a delivered task, or says: acceptance demo, accept demo, 受け入れ判断, 受入レビュー, ship/wait/reject 判定, 検収レビュー. Do NOT load for: implementation, code review, release work.

Extract recurring failure patterns from breezing orchestration logs and Judgment Ledger, emit failure-rule.v1 proposals with confidence scores. SSOT promotion to patterns.md or decisions.md is proposal-only — human-approval-required. Use when user mentions failure codifier, failure patterns, self-learning loop, codify failures, or failure-rule proposals. Do NOT load for: direct SSOT edits, auto-promotion, or implementation unrelated to failure analysis.

Configure and verify the Cursor backend for Claude Code Harness. Use when user invokes cursor:setup, wants Cursor as the local default implementation backend, or asks to check Cursor plugin/agent readiness. Distribution default remains opt-in; only local env/user settings are changed when explicitly requested.