thaitype

Chief Tribe

Name: Chief Tribe
Author: thaitype

AI community

SOURCE https://github.com/thaitype/chief-tribe

Description

Home of sage, chief, and chieftain — three layers for AI coding agents: baseline behavior, portable framework, full distribution.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

The Chief Tribe

A three-layer architecture for working with AI coding agents — without locking yourself into any single tool.

The Chief Tribe is an ecosystem of three open-source projects that together address **harness engineering** — the practice of designing what wraps around an AI model to turn it into a useful agent. Each layer serves a different purpose, and you can adopt them independently or as a full stack.

┌─────────────────────────────────────────────────────┐
│  chieftain                                          │  👑
│     Fully harnessed runtime + opinionated defaults  │
│  ┌───────────────────────────────────────────────┐  │  ⚔️
│  │  chief                                        │  │
│  │     Portable framework + workflow structure   │  │
│  │  ┌─────────────────────────────────────────┐  │  │
│  │  │  sage                                   │  │  │  🧙 
│  │  │     Baseline behavior principles        │  │  │
│  │  └─────────────────────────────────────────┘  │  │
│  └───────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────┘

Members of the Tribe

Project	Role	Opinion Level	Status
sage 🧙	Baseline behavior principles for any agent	None	Planned
chief ⚔️	Portable multi-agent workflow framework	Low	Active (formerly `chief-agent-framework`)
chieftain 👑	Opinionated runtime + distribution	High	Planned

Why Three Layers?

Different people need different things. A developer trying out an agent for the first time has nothing in common with a developer who wants a ready-to-ship workflow for their Azure project. Forcing them into the same tool produces something that serves neither well.

The tribe separates concerns: