yansfil

Project-local PRD writer. Use when the user invokes "$gen-prd", asks for a PRD, product requirements document, implementation-ready requirements, or wants to turn intake/clarify output into a human-reviewable requirements contract with major technical…

All-in-one PRD pipeline runner. Use when the user invokes "$please", asks to take the current conversation and carry it through to a finished implementation in one shot, wants the gen-prd then implement then ship chain run automatically without approval…

Project-local approved-PRD implementation executor and Observer entrypoint. Use when the user invokes "$implement", explicitly asks to execute an approved PRD through the receipt-backed workflow, or wants PRD tasks implemented and proven through one unified…

Project-local PRD pipeline configuration. Use when the user invokes "$sasu-setup", asks to enable or change PR delivery mode, configure worktree/secrets sync for implement, configure the agents/ namespace gitignore policy, inspect the current PRD pipeline…

Deliver a completed `implement` receipt locally or through GitHub PR delivery. Use when the user invokes "$ship" or explicitly asks to create a local implementation commit, open or update a PR, push a completed PRD implementation, watch CI, or merge an…

Project-local pre-PRD requirements interview. Use when the user invokes "$interview-me", asks to interview an idea, clarify or pressure-test requirements, reduce ambiguity, prepare a PRD source, or wants UX, behavior, scope, technical, verification, risk,…

Session-context quick pipeline: contract, implement, verified receipt. Use when the user invokes "$quick", asks to implement something small from the current conversation without the PRD pipeline, or wants the minimal path that still ends in a machine-checked…

Red-team a conclusion that is already on the table: take the dissenting opinion seriously, investigate it on its own terms, then rule on it. Use when the user invokes "$challenge", types the "!rv" trigger, says "반박해봐", "이거 아니라는데", "다시 검증해봐", "red team this",…

Use when the user asks Claude Code to execute an approved PRD or scoped task. Read the requirements, create a live checklist, implement the smallest safe changes, and keep acceptance criteria and verification evidence tracked.

Use before declaring a task complete, after code/content/config changes, or when the user asks to verify, QA, smoke test, validate, or inspect whether something really works. Inspect the changed scope, run the right checks, verify runtime behavior when…

Use when the user asks for a codebase health check, structural cleanup, or refactor without a specific bug or feature in mind - phrases like "코드 정리해줘", "구조 점검해줘", "리팩토링 리포트 만들어줘", "정리하면 좋을 곳 점검해줘", "clean up this codebase", "refactor report", or "what's messy…

운영 중인 웹 서비스의 최근 상태(기본 24시간)를 서비스 운영 데이터·배포 플랫폼·백엔드 로그 세 영역에서 점검하고, 결과를 "정상 / 주의 / 확인 필요"로 요약한 뒤 사람이 바로 봐야 할 것과 재현·조사가 필요한 것으로 나눠 보고한다. 사용자가 "운영 상태", "모니터링", "헬스 체크", "서비스 상태 확인", "최근 N시간 상태", "지금 문제 없어?", "대시보드", "monitoring / health check / ops status" 같은…

런칭 전/배포 전 웹 앱 보안 점검을 사용자 권한 관점과 서비스 운영 관점으로 나눠 수행하고, 결과를 "바로 고칠 것 / 사람이 결정할 것 / 반복 점검할 것"으로 정리한다. 사용자가 "보안 점검", "보안 리뷰", "런칭 전 점검", "security check/review/audit", "취약점 확인", "권한/인가 점검", "RLS 확인", "이 앱 안전한지 봐줘" 같은 요청을 하거나, 배포·런칭·오픈 직전에 안전성을 확인하려 할 때 이 skill 을…

Use when the user has an idea, feature request, design direction, or product problem that is still ambiguous. Ask focused questions before PRD or implementation, and turn the answers into a short handoff summary.

Use near the end of a session when a repeated mistake, useful verification command, project rule, workflow decision, or skill improvement should be preserved for future Claude Code sessions.

Use when preparing changed work for a pull request. Inspect git status and diff, keep unrelated work out, summarize the change, gather verification evidence, and draft a concise PR title and body.

Use when the user asks Claude Code to execute an approved PRD or scoped task. Read the requirements, create a live checklist, implement the smallest safe changes, and keep acceptance criteria and verification evidence tracked.

Use when the user asks for a PRD, implementation-ready requirements, or wants to turn clarify output into a scoped build document with requirements, acceptance criteria, tasks, and verification.

Use before declaring a task complete, after code/content/config changes, or when the user asks to verify, QA, smoke test, validate, or inspect whether something really works. Inspect the changed scope, run the right checks, verify runtime behavior when…

로컬 머신과 원격 머신 사이에서 Claude Code 세션과 작업환경을 통째로 넘기고 되받는다. 사용자가 "/handoff", "/handback", "원격으로 넘겨", "저쪽에서 이어서", "이동해야 하니 넘겨줘", "돌아왔으니 가져와", "회수해줘", "핸드오프 상태", "원격 정리" 라고 말할 때 사용한다. 넘기면 원격이 같은 대화 컨텍스트 그대로 자율 실행한다. 되받을 때는 파일만 회수하고 로컬 세션은 건드리지 않는다.

로컬 머신과 원격 머신 사이에서 작업환경을 넘기고 되받는다. 사용자가 "/handoff", "/handback", "원격으로 넘겨", "저쪽에서 이어서", "돌아왔으니 가져와", "회수해줘", "핸드오프 상태", "원격 정리" 라고 말할 때 사용한다. Codex 경로는 파일과 작업환경만 넘기고 원격에서 새 Codex 세션을 시작한다.

Ask one free-form problem question plus 7 structured workshop intake questions, inspect the current Claude Code project and user-input session patterns, then write a simple harness report.

Use when the user wants a hand-drawn sketchnote-style infographic that summarizes a document, article, Notion page, or topic into one image. Triggers on "스케치노트", "인포그래픽으로 만들어줘", "sketchnote", "이거 한 장으로 요약해줘", "요약 이미지", "비주얼 요약", or "/sketchnote". Not for…

Add a principle to the oh-my-principle repository, and review the set while doing it. Use when the user invokes "/principle", says "이거 원칙으로 추가해줘", "원칙에 넣어줘", "add this as a principle", "이 원칙 중복 아니야?", "원칙 정리해줘", or hands over an incident they want turned into…

Create and edit presentation decks (deck.json scene graph) through the presentation-king MCP tools. Use when the user asks to make slides, edit a deck, or respond to pinned selections from the presentation-king editor.