Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

docs: add lightweight contribution coordination guidance

tt-a1i442a748bd7b9
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7085b43b..40a29c5e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -13,6 +13,17 @@ Archify is Agent-first: people describe systems, and the Skill, typed JSON, rend
Do not include secrets, access tokens, credentials, private repository content, personal data, or customer data in fixtures, logs, screenshots, artifacts, or package tests.
+## Coordinate related work
+
+These steps apply to contributors, maintainers, and Agents:
+
+- Before implementing, search existing issues and open PRs for the same problem, including related fixes under review.
+- On the relevant issue, briefly state your intended scope and link a draft PR early. For a small fix without an issue, describe the scope in the PR; a separate planning issue or maintainer approval is unnecessary.
+- If work is already in progress, discuss the remaining gap on that issue or PR and agree on collaboration, a distinct scope, or consolidation before starting an overlapping implementation.
+- When consolidating, link both PRs, explain which contributions are retained, and preserve attribution through original commits or appropriate co-author credit. Close the superseded PR once the retained contribution and attribution are present in the continuing PR.
+
+A scope comment signals active work, not permanent ownership. If work pauses or changes direction, leave an update; others can propose taking it forward in the same thread.
+
## Prepare a reviewable change
Start from the latest `dev` and target `dev` for fixes and features. Check whether its existing controls already solve the reported case. Record the comparison base and candidate head.