메뉴
Run Boris Cherny's plan-first workflow — write a complete plan, get explicit approval, then execute. Use at the start of any complex task to avoid wasted work and mid-session corrections. Named after Boris Cherny, creator of Claude Code.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/hamzafarooq/claude-code-starter --skill boris-plan명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Research emerging trends in a market or technology space. Returns signal vs noise breakdown with evidence. Use when the user asks what's changing in a market, what trends to watch, or what's coming next.
Turn any document, proposal, report, or outline into a stunning single-file HTML presentation using 34 pre-built professional templates. Use when the user wants to convert a markdown file, proposal, or written content into a beautiful visual HTML document ready to share or convert to PDF.
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | boris-plan |
| description | Run Boris Cherny's plan-first workflow — write a complete plan, get explicit approval, then execute. Use at the start of any complex task to avoid wasted work and mid-session corrections. Named after Boris Cherny, creator of Claude Code. |
This skill enforces the workflow Boris Cherny (creator of Claude Code) uses for every complex task: plan first, execute second, verify last. Credit: Boris Cherny via howborisusesclaudecode.com.
Ask the user: "Describe the task you want to accomplish."
Then produce a plan — do NOT write any code or make any changes yet:
One sentence restatement of the goal. Flag any ambiguity here before proceeding.
List every assumption. If any are wrong, this is the time to correct them.
Numbered list. Each step is specific enough that you can verify it happened.
Explicitly name things that are out of scope — adjacent improvements, refactors, style changes — that you might expect but aren't in this plan.
Specific check: a command to run, a behavior to observe, a test that should pass.
[Small: <30 min | Medium: 30–90 min | Large: >90 min] — and why
Waiting for your approval before writing a single line.
Reply "approved", suggest changes, or ask questions. Only after approval will execution begin.