📝 TEMPLATE: This is the dot-agents AGENTS.md template. Customize it for your project by filling in the sections below. Delete this banner when done.
[Brief project description - update this for your project]
- Language: [e.g., TypeScript, Rust, Go, Python]
- Framework: [e.g., React, Express, Axum, FastAPI]
- Database: [e.g., PostgreSQL, SQLite, MongoDB]
Research → PRD → Plan → Execute
- Research: Investigate problem space, save findings to
.agents/research/ - PRD: Define requirements and acceptance criteria in
.agents/prds/ - Plan: Break PRD into executable tasks with Ralph-ready format
- Execute: Ralph runs tasks autonomously, commits after each
project/
├── AGENTS.md # This file - project instructions
├── .agents/
│ ├── reference/ # External repos (gitignored)
│ ├── research/ # Research and reference material
│ ├── prds/ # Product requirements documents
│ ├── plans/ # Implementation plans
│ │ ├── todo/ # Planned but not started
│ │ ├── in-progress/ # Currently being worked on
│ │ └── completed/ # Finished and verified
│ └── skills/ # Agent skills
│ ├── adapt/ # Project analysis and AGENTS.md setup
│ ├── ralph/ # Autonomous implementation loops
│ ├── research/ # Deep research workflow
│ └── tmux/ # Background process management
└── src/ # Source code
| Command | Effect |
|---|---|
Run adapt |
Analyze project and fill in AGENTS.md sections |
Research [topic] |
Deep investigation, saves to .agents/research/ |
Run ralph on [plan.md] |
Autonomous execution of plan tasks |
Skills are loaded via natural language. See each skill's SKILL.md in .agents/skills/ for details.
Plans in .agents/plans/ follow this workflow:
| Status | Location |
|---|---|
| TODO | plans/todo/ |
| IN-PROGRESS | plans/in-progress/ |
| COMPLETED | plans/completed/ |
Completing plans: When moving a plan to completed/, also move its corresponding .progress.md file if one exists.
Archive command: When asked to "archive completed plans", delete each plan from completed/ with its own commit. Git history preserves them.
- [ ] **Task N: Short descriptive title**
- Scope: `path/to/affected/files` or module name
- Depends on: Task M (or "none")
- Acceptance:
- Specific, verifiable criterion 1
- Specific, verifiable criterion 2
- Notes: Optional implementation hintsTask markers:
| Marker | Meaning |
|---|---|
- [ ] |
Not started |
- [x] |
Completed |
- [ ] (blocked) |
Blocked, needs intervention |
- [ ] (manual-verify) |
Requires manual verification |
# Add your project-specific commands here
# Examples:
# npm install / npm run dev / npm test
# cargo build / cargo test
# go build / go testgit status
git add -A
git commit -m "Description of changes"
git push- Write clear, descriptive commit messages
- Reference plan numbers in commits (e.g., "Plan 001: Initial setup")
- Commit after each logical step
After making changes:
- Update AGENTS.md - Keep project structure and commands current
- Update README.md - Reflect user-facing changes
- Update plan status - Move completed plans to
completed/
- [Naming conventions]
- [Code style preferences]
- [Commit message format]
[Brief description of project structure and key components]