菜单
Turn a repo-local spec, rollout doc, design note, or implementation plan into a compact /goal prompt. Use when the user wants to run Codex /goal from an existing spec-first workflow and needs the goal to preserve scope, non-goals, validations, and local constraints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | spec-to-goal |
| description | Turn a repo-local spec, rollout doc, design note, or implementation plan into a compact /goal prompt. Use when the user wants to run Codex /goal from an existing spec-first workflow and needs the goal to preserve scope, non-goals, validations, and local constraints. |
Create a /goal prompt from the user's existing planning artifact. The goal is
not to replace the spec; it is to turn the spec into a bounded execution prompt
that another Codex session can follow.
/goal.If the spec is too ambiguous to produce a safe goal, do not bluff. Ask the smallest question that would change the implementation scope, or produce a draft goal with the ambiguity called out as a decision point.
Use plain Markdown unless the user asks for another format.
Implement <specific slice> in <repo/worktree> on <branch>.
Source of truth:
- <spec path>
- <rollout or supporting doc path>
Scope:
- <required work item>
- <required work item>
Non-goals:
- <deferred phase or out-of-scope area>
- <compatibility boundary>
Preserve:
- <dirty/untracked/user-owned files or branches>
- <no-push/no-commit/approval constraints>
Validation:
- <exact command>
- <exact command>
Before finishing:
- Compare the diff back against <spec path>.
- Report implemented items, validation results, blocked items, and any
intentional fail-closed behavior.
/goal.Evaluate a repository's first-rung readiness for high-quality AI code contributions and produce concrete, copy-pasteable file changes that make the repo AI-ready. Use when asked to audit AI contribution quality, diagnose why AI PRs are low quality, prepare a repo for AI-assisted engineering, or move a repo from no harness toward a basic v0.5 contribution harness.
Bootstrap a small, deterministic repo-local AI harness by adding only the docs, skills, or checks that have concrete repo-specific content. Use when a repo already has basic AI contribution readiness and the user wants continuous harness improvement without placeholder process.
Evaluate a real AI-assisted work session against the repo-local harness, classify reusable misses, and update or propose updates to docs, skills, scripts, MCP/tooling, or sensors. Use after substantial work, review feedback, failed validation, or human correction in a repo with an AI harness.
Investigate established Pulumi-vs-Terraform parity gaps in bridged providers by creating or refining bridge cross-tests, after routing has already determined that bridge parity work is the next step, or when the user explicitly asks for that help. Use when the agent already knows that Pulumi has the problem and Terraform does not, and the next step is to capture, narrow, and explain that parity gap inside pulumi-terraform-bridge without debating alternate harnesses.
Run Claude Code as a chat-only reviewer for a local diff or branch, including adversarial pressure-testing when requested. Use when the user explicitly wants a Claude second opinion without posting GitHub comments.
Work back and forth with the user to understand intent, success criteria, constraints, and open questions before or during implementation. Use explicitly when the task is fuzzy, high-context, or benefits from shared thinking rather than immediate execution.