القائمة
Compressed response mode. Use when user wants terse replies, less tokens, caveman mode, or /caveman.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | caveman |
| description | Compressed response mode. Use when user wants terse replies, less tokens, caveman mode, or /caveman. |
Global response style when active or included by AGENTS.md.
ACTIVE EVERY RESPONSE. Off only: stop caveman or normal mode.
Say less. Keep technical substance exact. Fragments OK.
Korean: casual, terse, no honorific or polite endings. Avoid -습니다, -합니다, -요.
Prefer noun endings like 추가, 연결, 적용, 확인, 수정.
Initial-consonant shorthand OK when clear.
Code, commands, filenames, errors: exact.
Drop articles, filler, pleasantries, hedging, repeated words.
Use short words. Prefer [thing] [action] [reason]. [next step].
Compress repeated paths/lists with common prefix, globs, or ranges.
Unified scoped code review + parent-owned fix loop. Use for /review-loop, review until clean, code review with fixes, or modes: web, server, database, node, planning.
Orchestrate implementation work from intake to closeout. Use when the user asks to run a task through a consistent work flow, plan first, turn a plan into Taskwarrior tasks, execute task-by-task, verify, review, and optionally prepare commits. Trigger phrases include workstream, 작업흐름, 작업 흐름, 기획부터 태스크화, 계획 세우고 구현, and 태스크화해서 구현.
Convert implementation plans, Markdown checklists, and work items into a Taskwarrior task queue. Use when the user asks to queue, taskify, 태스크화, 작업 큐, 작업 등록, plan to tasks, checklist to tasks, or when workstream needs a Taskwarrior draft from plan Work Items. Shows a concise user-language summary before mutation and delegates command safety to the taskwarrior skill.
Close out implementation work by checking plan completion, Taskwarrior queue status, validation results, review findings, git status, residual risk, and commit readiness. Use when the user asks to close, finish, wrap up, 마감, 완료 정리, 종료 정리, or when workstream reaches its closeout phase. Does not commit by itself; delegates commits to git-commit only when requested.
Map a repository or working directory before implementation. Use when the user asks to survey, scan, inspect, orient, 구조 파악, 훑어보기, 작업 전 파악, or when workstream needs a pre-implementation map of project structure, package manager, commands, tests, local apps, ownership boundaries, and risk areas. Produces concise findings and recommended next checks without making code changes.
Choose and run validation for code, docs, config, UI, API, database, refactor, and bugfix work. Use when the user asks to verify, validate, test, confirm, check, 검증, 확인, 테스트, or when workstream needs a consistent validation matrix before marking tasks done. Produces focused checks, pass/fail criteria, and exact skipped or blocked validation gaps.
