본문으로 건너뛰기
cccskills
무료GitHub에 공개

turboplan

Analyze task complexity and route to a mode by artifact: direct fix for clear-scope changes, or a plan file when the approach needs to be written down. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(3)

  • SKILL.md2.5 KB
  • references/direct-mode.md476 B
  • references/plan-mode.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Turboplan

Analyze task complexity to recommend an execution mode, then let the user set the final route.

Categorize the user-supplied task along these dimensions using subjective judgment. This analysis makes the recommendation informed:

  • Scope: single feature / single subsystem vs multi-feature / multi-subsystem
  • Stakes: one-off change vs long-lived project with architectural implications
  • Unknowns: clear approach vs needs exploration and product decisions

Modes are named by what they produce: no plan, or a plan file.

ModeCriteriaRoute
DirectClear scope, with any remaining decisions small enough to settle in conversation rather than write down. Aligns on the shape, then implements.Read references/direct-mode.md and follow its steps.
PlanThe approach warrants writing down before implementing — to survey patterns, settle architectural decisions, or survive a fresh session. Produces a plan file, however large the work turns out to be.Read references/plan-mode.md and follow its steps.

Recommend and Confirm the Route

Form a recommended route from the dimensions and criteria above. Output the recommendation as text: the recommended mode and a line or two on why it fits over its neighbor.

Then use AskUserQuestion to have the user set the final route. Offer the recommended mode first, marked "(Recommended)", alongside the other mode; the auto-appended "Other" lets the user describe a different path.

Add a third Get a second opinion option whenever committing to the wrong mode would cost a session of rework, and whenever the recommended mode does not earn "(Recommended)" with conviction. It runs the /consult-codex skill for the soundest route given the task's scope, stakes, and unknowns. Then resolve the route with that answer in hand, re-asking when the choice stays the user's.

Carry the confirmed route into its reference file from the table above and follow its steps.

Rules

  • Diff size, perceived task simplicity, and context window concerns are not reasons to skip the chosen mode's phases.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

Audit the turbo skill lessons that /self-improve writes into this repo's .turbo/handoff/ from other projects, apply the ones the user approves, delete the consumed handoffs, commit and push, and update the installed Turbo skills. Use when the user asks to "read .turbo/handoff and let me know what you think", "read the handoff files and let me know what you think", "review the lesson handoffs", "apply the self-improve handoffs", or "process the turbo handoffs".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to "claude print", "ask claude", "run claude", "consult claude", or when a Codex Turbo skill needs Claude as an independent peer reviewer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tobihagemann/turbo4142026년 10월 17일 업데이트

tobihagemann의 스킬 모두 보기

이 스킬의 문제 신고