From 982c311356bd76f2605339588059150bb6b98492 Mon Sep 17 00:00:00 2001 From: BREW <81044362+b-re-w@users.noreply.github.com> Date: Fri, 2 Oct 2026 10:57:45 +0900 Subject: [PATCH] Docs: Land every feature through an issue and a pull request New features start by searching the issues, open one when none covers the work, and reach develop through a pull request that closes it. --- AGENTS.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 25891b56..266f01da 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -56,6 +56,18 @@ build caches, model weights, `node_modules`) into every worktree is how 86 workt root, and `docs/` keeps only its subdirectories (no Markdown files directly under `docs/`). CI runs `tools/release/sync-release.sh` (`.github/workflows/release-sync.yml`) to produce that layout; do not hand-edit `release` or `main`. +### Issues and pull requests + +Every new feature goes through an issue and a pull request: + +1. Before starting, search the repository's issues (`gh issue list --state all --search ""`). +2. If no issue covers the work, open one (`gh issue create`) stating what and why, and the + completion criterion — which tests must pass. +3. Work on a `work/` branch, push every commit, and open a pull request into `develop` + whose body contains `Closes #`. +4. Merge into `develop` through that pull request (`gh pr merge`), not by a local merge, so the + issue is linked and closed. + ## 5. Intent → Spec → Test → Code This project runs on **intent-based spec-driven development** and **test-driven development**.