영어 |**

網頁標題 지프 v5 알파는 여기에 ** — Story/Ticket 모델, /chief-wayfinder, /chief-loop] Ticket-frontier 실행 — 이제는 평행 모드(/chief-loop parallel:3)로 구축 한 번에 여러 티켓, 자체 격리 된 git worktree에서 각각 - 더 많은 시약 로스터. 공개 알파, 테스트 준비. · 설치: npx skills@latest add thaitype/chief#release/v5 · 릴리스 노트 · docs에 release/v5] · 이 README는 현재 안정된 ** v4.2.0 선을 설명합니다.

AI 코딩 에이전트의 구조 작업 흐름. 어떤 프로젝트로 드롭하면 규칙을 한 번 설정하고 코드베이스를 다시 설명합니다.

최고는 최고 수준의 생태계의 일부입니다. 그것은 그것의 행동 기본으로 sage를 사용합니다.

왜 최고 존재

모든 프로젝트는 컨텍스트가 있습니다 - 6 개월 전의 결정, 이상한 일, 모든 "왜 우리는이 방법을 수행"물. 그것은 당신의 머리에 살고. 모든 새로운 AI 채팅은 빈을 시작, 그래서 당신은 re-explain. 그런 다음 다시 채팅.

최고 정지 그. 모든 프로젝트는 동일한 형태를 부여합니다 - [T5]] 규칙에 대한, .chief/_rules/] 표준에 대한, .chief/milestone-N/] 현재 작업에 대한. 에이전트는 읽고 쓰는 곳을 알고. 당신의 프롬프트는 하나의 문장으로 축소합니다.

Chief ⚔️

English | ไทย

📣 Chief v5 Alpha is here — Story/Ticket model, /chief-wayfinder, /chief-loop ticket-frontier execution — now with a parallel mode (/chief-loop parallel:3) that builds multiple tickets at once, each in its own isolated git worktree — no more subagent roster. Public alpha, ready for testing.

Install: npx skills@latest add thaitype/chief#release/v5 · Release notes · docs on release/v5

This README describes the current stable v4.2.0 line.

A structured workflow for AI coding agents. Drop it into any project, set your rules once, and stop re-explaining your codebase every chat.

Chief is part of the chief-tribe ecosystem. It uses sage as its behavioral baseline.

Why Chief exists

Every project has context — the decisions from six months ago, the weird workaround, all the “why we do it this way” stuff. It lives in your head. Every new AI chat starts blank, so you re-explain. Then again next chat.

Chief stops that. Give every project the same shape — AGENTS.md for rules, .chief/_rules/ for standards, .chief/milestone-N/ for current work. Agents know where to read and write. Your prompts shrink to one sentence.

→ Why Chief exists

Quickstart

Step 1 — Install skills:

npx skills@latest add thaitype/chief

Select the skills you want. Make sure chief-install is included.

Step 2 — Run /chief-install in your agent:

/chief-install

It asks which coding agent you use, whether to symlink or copy, and whether to include subagents. That’s it.

Step 3 — Bootstrap project context (optional):

/chief-init

Interviews you about your stack and dev commands, writes .chief/project.md. Skip it and write the file by hand later if you prefer.

→ Full tutorial: your first milestone→ Manual install options

Windows users: Symlink mode requires Developer Mode and git config --global core.symlinks true. The install skill auto-detects and falls back to copy mode.

How Chief works

Chief is markdown files in three places:

project/
├── AGENTS.md          ← framework + project rules (highest authority)
└── .chief/
    ├── project.md     ← tech stack, dev commands (written by /chief-init)
    ├── _rules/        ← standards that apply across all milestones
    └── milestone-1/   ← current work: goals, contracts, tasks

.chief/ is created lazily — nothing appears until you need it.

Rules hierarchy: AGENTS.md > .chief/_rules/ > .chief/milestone-N/_goal/. Higher always wins.