跳到正文
cccskills
免费在 GitHub 公开

plan

Turns implementation requests into concise work plans with file references, testable acceptance criteria, risks, and verification steps. It can clarify vague requirements through focused questions, generate a plan directly, or review an existing plan.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Lightweight planning with optional interview

查看安装方法

适用场景

  • Clarifying vague requirements before implementation
  • Creating a plan with testable acceptance criteria
  • Reviewing an existing work plan

包含的文件(1)

  • SKILL.md3.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

<Purpose> Plan creates concise, actionable work plans. Auto-detects interview vs direct, supports `--interview` for Socratic clarification and `--review` for evaluation. </Purpose>

<Use_When>

  • Planning before implementation — "plan this", "let's plan"
  • Requirements are vague and need scoping — use --interview
  • Reviewing an existing plan — --review </Use_When>

<Do_Not_Use_When>

  • Want direct execution — execute the scoped task directly; use ultragoal only for durable goals or team for coordinated parallel work
  • Simple focused fix with obvious scope — skip planning </Do_Not_Use_When>

<Execution_Policy>

  • Auto-detect interview vs direct; --interview forces Socratic mode, --direct skips it
  • Ask one question at a time; gather codebase facts first
  • omx explore is deprecated. Use normal repository inspection for codebase facts; omx sparkshell only for explicit shell-native evidence
  • Plans must be evidence-backed: 80%+ claims cite file/line, 90%+ criteria testable
  • Right-size steps to scope; save to .omx/plans/ </Execution_Policy>
<Steps>

Mode Selection

ModeTriggerBehavior
Interview--interview or broad requestSocratic requirements gathering
Direct--direct or detailed requestGenerate plan immediately
Review--reviewCritic evaluation of existing plan

Interview (--interview)

  1. Classify request; ask one focused question via omx question
  2. Gather codebase facts first, then ask informed follow-ups
  3. Build on answers; consult Analyst for hidden requirements
  4. Create plan when user signals readiness

Direct

  1. Quick analysis (optional Analyst)
  2. Generate plan immediately
  3. Optional Critic review if requested

Review (--review)

  1. Read plan from .omx/plans/
  2. Evaluate via Critic; verdict APPROVED/REVISE/REJECT
  3. If author == reviewer, hand off to $code-review

Output

Every plan includes: Requirements Summary, Acceptance Criteria (testable), Implementation Steps (with file refs, adaptive count), Risks/Mitigations, Verification. Saved to .omx/plans/.

Outcome-first framing: apply outcome-first framing, concise visible updates for multi-step planning. Local overrides for the active workflow branch apply via newer user task updates. If the user says continue, continue the current branch instead of restarting.

</Steps>

<Tool_Usage>

  • omx explore is deprecated. Use normal repository inspection; omx sparkshell only for explicit shell-native evidence
  • Use omx question for interview questions; plain text only as fallback
  • Use ask_codex with planner/analyst/critic as needed </Tool_Usage>

<Escalation_And_Stop_Conditions>

  • Stop interviewing when requirements are clear — do not over-interview
  • Escalate on irreconcilable trade-offs requiring business decision
  • "just do it" / "skip planning" → hand off to $ultragoal </Escalation_And_Stop_Conditions>

<Final_Checklist>

  • Acceptance criteria testable (90%+ concrete)
  • Claims cite file/line (80%+)
  • Risks have mitigations, no vague terms
  • Plan saved to .omx/plans/ </Final_Checklist>
<Advanced> ## Question Classification | Type | Examples | Action | |------|----------|--------| | Codebase Fact | "Where is X?" | Explore first, do not ask | | User Preference | "Priority?" | Ask via `omx question` | | Scope Decision | "Include Y?" | Ask user |

Review Quality Criteria

CriterionStandard
Clarity80%+ claims cite file/line
Testability90%+ criteria concrete
VerificationFile refs exist
</Advanced>

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.

中文简介正在准备中。当前显示英语简介。

  • Simplify bloated or repetitive AI-generated code
  • Remove unused code and unnecessary wrappers
  • Review fallback paths that hide errors
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

analyze

免费

Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.

中文简介正在准备中。当前显示英语简介。

  • Investigate possible causes of a bug
  • Understand behavior across multiple files
  • Explain architecture and tradeoffs
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

ask

免费

Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.

中文简介正在准备中。当前显示英语简介。

  • Get a second opinion on a proposed approach
  • Ask Claude or Gemini to review work
  • Save brainstorming results for later use
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

autopilot

免费

Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.

中文简介正在准备中。当前显示英语简介。

  • Deliver an issue from requirements clarification through verification
  • Turn an initial idea into a reviewed implementation plan
  • Resume interrupted work from its saved phase
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.

中文简介正在准备中。当前显示英语简介。

  • Research with explicit acceptance criteria
  • Verify research results with a script
  • Require review approval before completing research
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.

中文简介正在准备中。当前显示英语简介。

  • Check the replacement for a removed research command
  • Update requests to use $autoresearch
  • Confirm which command owns the research mission lifecycle
Yeachan-Heo/oh-my-codex3.4万2026年10月21日 更新

查看 Yeachan-Heo 的全部技能

报告此技能的问题