Project Structure

The files prompter init creates and what each one is for.

Directory tree

This is what `prompter init` creates in your project. It's all plain text you can commit to git and review like code.

prompter/├── project.md          # Project conventions├── AGENTS.md           # Instructions for every agent├── CLAUDE.md           # Claude-specific instructions├── skills/             # Installed skills├── specs/              # Current truth — what IS built│   └── <capability>/│       ├── spec.md│       └── design.md└── changes/            # Proposals — what SHOULD change    ├── <change-id>/    │   ├── proposal.md    │   ├── tasks.md    │   ├── design.md    │   └── specs/    └── archive/        # Completed changes

What to commit

Commit `specs/` and `changes/` — that's the point. Specs become a shared record of what's built, and proposals can be reviewed in a pull request like any other code. The `skills/` directory is re-fetched by `prompter init`, so you may gitignore it if you'd rather keep the repo light.

Last updated: May 16, 2026