Gaps worth filling (still keep it short)

Gap Notes Suggested fix
Code-only Quick Start Implies everyone ships a PR Tiny Ways to contribute (docs, triage, examples, tests)
No claim step Risk of duplicate work After pick issue: comment to claim / confirm in Discord
No bug / feature hints AGENTS is agent-ops, not issue templates 3 bullets for bugs; 1–2 for features
PR bar is soft AGENTS already has PR hygiene + conventional commits One line: “follow PR hygiene in AGENTS.md” + focused / link issue / tests
Discord “why” list is long 5 bullets repeat the same idea Optional trim to 2–3 + Discord vs GitHub split
No CoC / recognition Neither file exists yet Optional one-liners; do not block the rewrite on new files

Proposed next CONTRIBUTING.md

# Contributing

We love contributions — code, docs, triage, examples, and tests.
Start on Discord so scope is clear before you invest time.

## Join us on Discord

[![Discord](<https://img.shields.io/badge/Discord-join%20the%20community-5865F2?style=for-the-badge&logo=discord&logoColor=white>)](<https://discord.com/invite/UZv7JjxbwG>)

**Daily contributor sync:** every day at **10:00 PM IST**

- **Discord** → questions, mentoring, sync, realtime unblocking
- **GitHub** → bugs, proposals, design threads, review

Non-trivial work? Comment on the issue or ping Discord first. Get a thumbs-up, then build.

## Ways to contribute

| Type | Examples |
| --- | --- |
| Code | Fixes, features, adapters, performance |
| Docs | README, docs/, architecture notes |
| Triage | Repro bugs, tighten reports, label suggestions |
| Examples / tests | Recipes, edge cases, flaky-test hunts |

## Quick start

1. **Join Discord** — say hi and get guidance
2. **Read the contract** — [AGENTS.md](AGENTS.md) (layout, commands, hard rules, PR hygiene)
3. **Pick something focused** — [open issues](<https://github.com/AgentWrapper/agent-orchestrator/issues>); prefer `good first issue` / `help wanted`
4. **Claim it** — comment `I'd like to work on this` and wait for assignment
5. **Open a clear PR** — narrow change, link the issue, user-visible impact, tests
6. **Iterate** — address review; maintainers merge

Need the product/run overview first? Start with [README.md](README.md) and [docs/architecture.md](docs/architecture.md).

### Bug reports

Include `ao` version, OS, repro steps, expected vs actual, and relevant daemon/logs context when you can.

### Feature ideas

Lead with the problem and who it helps — not only the solution.

### PR bar

Follow **PR hygiene** in [AGENTS.md](AGENTS.md): branch from `main`, one issue per PR, conventional commits, explain intentional omissions. Keep CI green for the area you touched.

## Code of Conduct

Be respectful, constructive, assume good intent. Report problems to maintainers via Discord DM.

Thanks for making agent-orchestrator better for the next person who shows up.

Shipped in repo