This is an automated email from the ASF dual-hosted git repository. spmallette pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 83ddf8c07f4fe6f39ade4360f16281bdc66c9cbb Author: Stephen Mallette <[email protected]> AuthorDate: Fri Aug 7 16:29:54 2026 -0400 Point every session at beads from AGENTS.md, not just tinker-dev Beads applies to any TinkerPop session, whichever skill is active, so the 'run bd prime if installed' pointer belongs in AGENTS.md. tinker-dev's Beads Caveats duplicated four rules PRIME.md already states, so they are dropped rather than moved. Assisted-by: Claude Code:claude-opus-5 --- .skills/tinker-dev/SKILL.md | 23 +---------------------- AGENTS.md | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+), 22 deletions(-) diff --git a/.skills/tinker-dev/SKILL.md b/.skills/tinker-dev/SKILL.md index 073473c552..ccf0d0728b 100644 --- a/.skills/tinker-dev/SKILL.md +++ b/.skills/tinker-dev/SKILL.md @@ -5,8 +5,7 @@ description: > testing, or contributing to TinkerPop's graph computing framework and its multi-language Gremlin ecosystem (Java, Python, JavaScript, .NET, Go). Covers coding conventions, build recipes, test evaluation, documentation, - development environment setup, Gremlin MCP server usage, and beads (bd) — - the agent planning and persistent memory system used by TinkerPop maintainers. + development environment setup, and Gremlin MCP server usage. license: Apache-2.0 compatibility: Requires Java 11+, Maven 3.5.3+, Docker. Individual GLVs may need Python, Node.js, .NET SDK, or Go. metadata: @@ -149,25 +148,6 @@ Otherwise, match the existing code in neighboring files — explicit imports (no `final` where practical, SLF4J logging over `println`, Hamcrest matchers, and closing any `Graph` you construct in a test. -## Beads Caveats - -The general agent Do/Don't rules are in the root `AGENTS.md`. **Run `bd prime` at the start of -a session and again after any context compaction** — it emits `.beads/PRIME.md`, the canonical -workflow. If `bd` is not installed, skip it; nothing else in this skill depends on beads. - -Four rules are easy to get wrong and worth repeating here: - -- Beads is the tracker for all work. Don't keep the plan in `TodoWrite`, `TaskCreate`, or a - markdown file — those are session-scoped, so nothing tracked there becomes memory. Create - the bead before writing code. -- Don't close a beads issue when a PR is submitted — close it only after the PR merges to the - target branch, then **pin** every bead in the subtree: root, decisions, records and tasks. - Pinning is what makes a bead permanent; everything destructive keys on `status=closed`. -- Never run `bd flatten`, `bd compact`, or `bd admin compact`. They rewrite or discard history - irreversibly, and `admin compact` destroys `--design` text specifically. -- Put rationale on the root or on a decision bead, not spread across task beads — scattered - that way, nobody finds it. - ## Reference Guides Build and validate commands live in the **Definition of Done** table above. For the remaining @@ -175,4 +155,3 @@ task-specific guidance, see: - [Development Environment Setup](references/dev-environment-setup.md) — fresh clone to working environment, prerequisites, GLV activation - [Gremlin MCP Server](references/gremlin-mcp.md) — translation, formatting, querying via MCP -- Beads workflow — run `bd prime` (emits `.beads/PRIME.md`): root binding, decision capture, pin-at-merge, structure conventions diff --git a/AGENTS.md b/AGENTS.md index 24d1038acc..57d0488c72 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,6 +13,25 @@ reference material for each Gremlin Language Variant. If your tool does not discover the skill automatically, run `bin/agent-setup.sh --list` to see how to configure it, or `bin/agent-setup.sh <agent>` to set up the integration. +## Planning and Memory: Beads + +TinkerPop maintainers use **beads (`bd`)** for planning and as the project's long-term +memory — it records not just what changed, but why: decisions made, alternatives rejected, +directions abandoned. + +**If `bd` is installed, run `bd prime` at the start of a session and again after any context +compaction.** It emits `.beads/PRIME.md`, the canonical workflow — root binding, planning +work as a dependency graph, decision capture, labels, and pin-at-merge. Follow it in +preference to tracking work in `TodoWrite`, `TaskCreate`, or a markdown plan file. + +```bash +command -v bd >/dev/null && bd prime +``` + +This applies to any TinkerPop session, whichever skill is active. If `bd` is not installed, +skip it — nothing else in this repository depends on beads. Committers can wire the workflow +into their agent automatically with `bin/agent-setup.sh --contributor`. + ## Canonical Documentation These local documents are authoritative. If this file appears to contradict them, treat them as canonical.
