Town Charter — Testing skill for Claude Code
A spec for AI-assisted multi-repo development workspaces.
How to install Town Charter
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open technicalpickles/town-charter and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Town Charter does
A spec for AI-assisted multi-repo development workspaces.
Alternatives in Testing
- OpenAgentsControl — AI agent framework for plan-first development workflows with approval-based execution 4.8k ★
- Cc Sdd — Spec-driven development (SDD) for your team's workflow 3.1k ★
- Flow Spec — NLSpec authoring — use when you need a structured specification from multi-AI research and consensus 2.8k ★
README
town-charter
A spec for AI-assisted multi-repo development workspaces.
What is a town?
A town is a git repo that organizes multiple external repositories, tracks work across them, and teaches AI assistants your conventions. It gives your development work a home that is versioned, shareable, and durable. Towns are meant to be inhabited: you commit plans, session handoffs, and working notes alongside the tooling that helps you navigate them.
What does that look like?
[Pickletown](examples/pickletown/README.md) is a working town that has been in daily use since early 2026, managing ~19 repositories across a Rails monolith, open-source tools, and infrastructure projects.
~/pickleton/
repos/
zenpayroll/
bare.git/
worktrees/
main/
gt-pw2k+add-oauth/
gusto-karafka/
bare.git/
worktrees/
main/
projects/
.claude/
.sessions/
Each repository is tracked as a bare clone with isolated working areas per branch. Multiple branches are active simultaneously, no stashing or switching required. A CLI (`pt`) ties it together: one command to check the status of a piece of work across its tracking item, branch, worktree, and PR.
The [Pickletown companion](examples/pickletown/README.md) maps each spec concept to its concrete implementation, with real commands, real output, and honest notes about what works and what is still rough.
What is this repo?
This repo is the spec. It describes the concepts, motivations, and interfaces that make a town work. It is for humans designing their workspace and AI assistants operating within one. There is nothing to install.
[Read the spec](spec.md)
Origin
[Gas Town](https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04) (Steve Yegge) is where the idea of a git-managed workspace directory with task tracking alongside code first clicked in practice. Pickletown took those structural patterns and built at a different point on the autonomy
Related Skills
Liminal Spec
Liminal Spec: spec-driven development methodology for AI-assisted coding. Claude Code skill.
Vibe Setup
A small Bash CLI that bootstraps a project for AI-assisted development: seeds AGENTS.md/CLAUDE.md, a secrets-d
Get Shit Done Multi
Fork of Get Shit Done (TÂCHES) with multi-CLI support. Spec-driven development workflows for Claude, Copilot,
SpecWeaver
Professional Claude Code plugin for AI-powered spec-driven development with automated code review and multi-ag
Spec Forge
Best AI-Powered Spec-Driven Development Tool 2026 - Multi-Agent Code Review & Automation
Sdflow Skills
Spec-driven development workflow for Claude Code / Codex: clarify → grill → generate the four artifacts, multi
Related Agents
Hub Architect
Thoughtbox Hub ARCHITECT agent. Joins workspaces, analyzes structure, designs solutions, creates proposals. Us
OSpec CLI
Document-driven OSpec workflow for AI-assisted development with change-ready initialization, execution, valida
2code
AI-assisted development produces a mess of parallel state: several terminals, experimental branches, uncommitt