first-tree-writelisted

Write Context Tree updates from explicit source material — code PRs, design docs, meeting notes, raw text. Use when the user gives you a concrete source and wants the right durable tree change drafted, linked, and reviewed. This skill is source-driven and targeted; use `first-tree-sync` instead for broad drift audits with no specific source.
agent-team-foundation/first-tree · ★ 7 · AI & Automation · score 74

Install: claude install-skill agent-team-foundation/first-tree

# First Tree Write Read these first: - `../first-tree/SKILL.md` - `../first-tree/references/anti-patterns.md` - `../first-tree/references/maintenance.md` ## What This Skill Does Take one specific source — a PR, a doc, a note — and produce zero, one, or a small set of tree changes that capture what's durable and decision- relevant. The output is a tree-repo PR linked to the source. ## When To Use This Skill | Use this skill | Use a different skill | | ------------------------------------------------------------ | ----------------------------------------------------------------------------- | | User pastes a PR link and says "reflect this in the tree" | User asks "is the tree up to date?" → `first-tree-sync` | | User pastes a meeting note about a decision | Repo is unbound → `first-tree-onboarding` first | | User pastes raw text and asks for the tree implication | A GitHub notification needs only a label / comment → `first-tree-github-scan` | | GitHub Scan agent classifies a notification as `route=write` | Audit drift since a release → `first-tree-sync` | ## The Default Stance Default to **not writing**. The tree compresses expensive context; a node nobody reads is worse than a missing node. If the source does not clearly establish a decision, constraint, ownershi