菜单
Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.
Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.
Review English technical prose without modifying it. Use for plain-English feedback on comments, docstrings, documentation, commit or pull request text, issues, reports, runbooks, logs, errors, command help, and other human-readable technical writing rather than factual or marketing review.
Audit or, when authorized, rewrite persuasive product claims against shipped-product evidence. Use for landing pages, marketing-heavy READMEs, feature or pricing pages, comparisons, and calls to action.
Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
| name | critical-journey-document |
| description | Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate. |
Create one canonical journey record in the repository's established product-documentation location.
english-text-review on the completed record and apply material findings without changing agreed contracts, identifiers, or domain terms.Acceptance sections describe product acceptance; test-design owns executable tests. Telemetry sections record agreed contracts rather than inventing events. repo-context-document owns implemented-system flows under docs/context/; rollout-readiness-review owns deployment readiness; spec-update owns semantic decisions.
Do not create a parallel canonical document, mandatory identifier system, speculative telemetry, or an artifact suite by default.
Finish when the record has evidence links, named ownership, explicit unknowns, and only sections with current consumers.