菜单
Define the fundamental purpose of a project or organization. Answers why the project exists; produces a single mission statement persisted to docs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Store, look up, or delete a personal credential (server SSH password, database password, website login, API key/token, certificate passphrase) in the macOS Keychain using a consistent <project>-<env>-<kind> naming scheme, and optionally record a pointer (never the secret itself) in the current project's Claude Code memory. Always use this skill whenever the user asks to save, store, remember, look up, rotate, or delete a password, API key, token, SSH credential, or database credential on this machine — even if they don't say "Keychain" or "security" explicitly, e.g. "save this database password so I don't lose it", "把这个数据库密码存一下", "记一条密钥", "这台服务器的密码帮我记下来", "what's the postgres password for staging again", "delete the old GitHub token from keychain". Do not use this for team-shared secret vaults, CI/CD secret injection, or anything that needs to sync across machines — those need a real secrets manager, not this skill.
Drain pending NATS messages from a producer contract via NATS MCP tools. Discovers the available NATS tool capabilities, selects exact-subject or wildcard mode from .cortex/nats.yaml, applies Tolerant Reader semantics, executes ack/nak/term decisions, and returns aggregated stats.
Audit and refactor existing SKILLs to meet spec compliance, repository asset boundaries, tool adaptation requirements, and LLM best practices.
From inside a linked worktree, deliver the current feature branch into main — merge with --no-ff, push, and optionally clean up the worktree, all without leaving CWD.
After code changes, auto-detect the project's build system and local deployment method for a given directory, then build the project and restart its locally-deployed environment (Docker Compose / systemd / process manager). Never assumes — asks only when detection is ambiguous. Caches detected commands per project in .cortex/redeploy-local.yaml; re-invocations on the same project skip re-scanning until signal files change, the cache expires (30 days), or the skill version bumps.
From the main repo on the main branch, scan all linked worktrees and local branches, let the user multi-select, then merge --no-ff + push them sequentially and clean up succeeded worktrees together.
| name | define-mission |
| description | Define the fundamental purpose of a project or organization. Answers why the project exists; produces a single mission statement persisted to docs. |
| description_zh | 定义项目或组织的根本目的；回答项目为何存在；产出 mission 陈述并持久化到 docs。 |
| tags | ["documentation","workflow"] |
| version | 1.4.0 |
| license | MIT |
| recommended_scope | both |
| metadata | {"author":"ai-cortex"} |
| triggers | ["define mission","mission","why we exist"] |
| input_schema | {"type":"free-form","description":"Project or product identifier; current understanding of purpose from docs, README, or user"} |
| output_schema | {"type":"document-artifact","description":"Mission statement written to docs/project-overview/mission.md (or project norms)","artifact_type":"mission","path_pattern":"docs/project-overview/mission.md","lifecycle":"living"} |
角色：战略链第一层，定义项目存在的根本目的 WHAT：单一使命陈述（1–3 句，仅说明"为何存在"） HOW：从 README/docs/用户处引出目的，与用户确认后写入约定路径 区别：愿景（未来状态）→
define-vision；指标 →define-north-star；目标 →design-strategic-goals
定义并记录使命：项目或组织存在的持久原因。使命陈述回答"为什么存在这个？"，注重结果（我们服务的目的）而非实施（我们如何做或我们构建什么），在路线图或功能变化时保持稳定。
首要目标：生成单一、用户确认的使命陈述，并持久化到约定路径。
成功标准：
docs/project-overview/mission.md，按项目 norms 覆盖）验收测试：新团队成员能否仅读使命就理解项目存在的原因？
本技能负责：引出根本目的；起草 1–2 句使命；与用户确认；写入约定路径。
本技能不负责（交接给指定技能）：
define-visiondefine-north-stardesign-strategic-goalsdefine-roadmap交接点：使命批准后 → 推荐 define-vision。
执行：
输入：项目标识符；对目的的现有理解（来自 README、docs 或用户）。
输出：使命陈述 Markdown 文档；路径见 frontmatter output_schema.path_pattern；生命周期 living。
输入：README 说"我们构建了一个支持 YAML 配置、回滚和审核日志的 CLI" 使命草案："我们的存在是为了为团队提供可靠、可审核的部署方式，并具有回滚和清晰的历史记录。"
为何正确：聚焦目的（可靠部署），不列功能（YAML、CLI）。
错误草案："我们构建了一个支持一键部署的 CLI，到 2027 年实现全行业最快回滚。"
问题：列出功能（"一键 CLI"）和指标/未来状态（"2027 年最快"）。功能属于产品文档，未来状态属于愿景。
背景：用户说"我们的部署工具需要一个使命，愿景稍后再考虑。"
流程：引出 who（工程团队）、问题（手动部署易错）、why（可靠性、安全性）。草案：「我们的存在是为了为工程团队提供单一、可靠的方式，将服务从代码部署到生产，将手动步骤降至最低、安全性提至最高。」用户确认 → 写入 docs/project-overview/mission.md。
背景：现有 mission.md 包含产品功能描述。
流程：读取现有版本，识别功能描述部分。提取目的：客户为何需要这个产品？起草精简版（仅目的）。覆盖前必须用户确认；保留旧版本到 git history 便于追溯。
识别：陈述中出现"到 YYYY 年"、"实现 X% 提升"、"成为最快/最大"等。
纠正：
define-vision 或 define-north-star 承接被移除的内容识别：陈述中出现"我们构建了 X"、"包含 A、B、C 功能"等。
纠正：将"我们构建了 X"重写为"我们的存在是为了 Y"，把功能视角转换为目的视角。