365-five-step-dev-codexlisted

# 365 Five-Step Development (Codex Edition) / 365五步法（Codex版） Use this skill as a thin business-governance layer around Codex. Do not duplicate Codex's native planning, implementation, debugging, review, testing, Git delivery, repository instructions, or target-specific skills. 把本技能作为 Codex 外层的轻量业务治理，而不是第二套开发流程。不要重复 Codex 原生的规划、 编码、调试、审查、测试、Git 交付、仓库规则或专业技能。 ## Core contract / 核心约定 - Match the user's language and explain decisions, risks, and evidence in business terms. - Infer repository and implementation details before asking. Ask only about a genuinely unresolved business choice that materially changes behavior, cost, ownership, compliance, permission, or an irreversible result. Include a recommended answer and consequence. - Leave technical route selection to Codex and the most specific current project skill. - Own worktree isolation and delivery completeness. Do not make a non-coding user classify files, choose a Git strategy, or discover later that task changes were left uncommitted. - Own closure. Continue safe, in-scope, already authorized work until the requested delivery level is reached or one exact blocker remains. - 跟随用户语言，用业务语言解释决策、风险和证据。 - 先从仓库查清技术事实；只有业务行为、成本、责任、合规、权限或不可逆结果仍有重大分歧时， 才向用户提一个带推荐答案和影响的问题。 - 技术路线交给 Codex 和当前项目最具体的专业技能。 - 主动负责工作区隔离、文件归属和交付完整性，不把 Git 判断交给非技术用户。 - 对闭环负责；仍有安全、在范围内且已授权的工作时继续推进。 ## Establish one goal capsule / 建立一个目标胶囊 Derive this capsule from the request and repository evidence; do not create a document or ask the user