purpose-tree
/purpose-tree
Opisuje metodę drzewa celów: jak czytać, pisać i sprawdzać pliki purpose-tree.yaml i architecture.yaml oraz oceniać, czy zmiana służy celom projektu.
- Autor
- JavanC ↗
- Repozytorium
- Homunculus ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 13
- Skrypty
- 3
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 3 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/tree.cjs, scripts/validate.cjs, tests/validate.test.cjs
Co robi i kiedy
Opisuje metodę drzewa celów: jak czytać, pisać i sprawdzać pliki purpose-tree.yaml i architecture.yaml oraz oceniać, czy zmiana służy celom projektu.
Oryginalny opis (EN)
The purpose-tree method — how to read, write, and check a project's tree of purposes (why each part exists) separately from its implementations (what currently realizes them). Use when creating, reading, editing, or validating purpose-tree.yaml or architecture.yaml, or when deciding whether a change serves a project's purposes.
Jak działa
- Where the tree lives
- Purpose, metric, realization
- Node format (v3.0)
- Top-down rule
- Health rules
- Validate
Podgląd SKILL.md
---
name: purpose-tree
description: The purpose-tree method — how to read, write, and check a project's tree of purposes (why each part exists) separately from its implementations (what currently realizes them). Use when creating, reading, editing, or validating purpose-tree.yaml or architecture.yaml, or when deciding whether a change serves a project's purposes.
---
A project's **purpose tree** records *why* each part of the project exists. Implementations
change often; purposes rarely do. Keeping them apart lets you replace any implementation
without losing sight of what it was for.
## Where the tree lives
- In the project, never in this skill: `purpose-tree.yaml` at the project root.
- If it is missing, look for the legacy name `architecture.yaml`. Read and update whichever
exists; do not rename it unless asked.
- Create the file lazily: only when the human states the first (root) purpose.
## Purpose, metric, realization
Each node separates three things that change at different speeds:
| Question | Field | Example | Changes |
|---|---|---|---|
| **Why** | `purpose` | "The user never drops a commitment, without having to remember it." | rarely |
| **What to achieve** | `metrics[].healthy` | "0 dropped commitments per week" | sometimes |
| **How, right now** | `realized_by` | "a morning brief at 08:00" | often |
If a `purpose` names a number or target, move it to `metrics`. If it names a tool, file, or
schedule, move it to `realized_by`. Then ask what it is *for*.
## Node format (v3.0)
A purpose is realized by a list of means. A means is either a **concrete implementation**
(a string) or a **sub-purpose** (an object with `purpose`). One list, two kinds — an item
with a `purpose` field is a sub-purpose; anything else is an implementation.
```yaml
version: "3.0"
root:
id: root
purpose: Why this exists (one sentence)
status: active | paused | planned # default active; retired nodes are deleted
status_note: Current state, known gaps
paused_reason: Required when paused or planned: why, and how to resume
metrics: [{name, source, healthy}]
tests: [test file patterns]
health_check: {command, expected} # exit 0 = healthy
realized_by:
- scripts/capture.js # implementation
- id: daily_awareness # sub-purpose: same node format, recursive
purpose: Know what matters before the day starts
realized_by:
- morning brief job
```
- Every sub-purpose needs a unique `id` so it can be referenced.
- All items in `realized_by` are needed together (AND). Alternatives (OR) are not modeled yet.
- If a sub-purpose is later replaced by a single tool, swap the object for a string.
- **Legacy trees:** a `goals:` map (key = id, value = node) is read as sub-purposes
appended to `realized_by`. Do not convert unless asked.
Field details and examples: [references/schema.md](references/schema.md).
Blank starting tree: [templates/purpose-tree.yaml](templates/purpose-tree.yaml).
## Top-down rule
1. The **human** sets the root and every upper purpose. You may draft them (each line labeled
with its source: a doc line or "inferred from code"), but never write or reword one the
human has not confirmed.
2. You may **propose** lower purposes under an existing one; the human accepts or rejects.
3. A child must serve its parent. If you cannot say how, it does not belong there.
4. Upper purposes change only in an explicit review — never as a side effect of daily work.
## Health rules
- **No false greens.** A `health_check` must fail when the data it judges does not exist.
`test -f`, `ls | head`, `wc -l`, or a `jq` that passes on an empty array are not checks.
- **No empty husks.** A `paused` or `planned` node must have a `paused_reason`.
- **No orphans.** Every node except root sits under a parent purpose.
## Validate
```bash
node <this-skill>/scripts/validate.cjs [path-to-tree]
```
Exit 0 = valid; exit 1 prints each problem. Run it after every edit to the tree.
Pliki w paczce (13)
- SKILL.md 4 KB
- references/schema.md 3 KB
- scripts/tree.cjs 3 KB
- scripts/validate.cjs 10 KB
- templates/purpose-tree.yaml 1 KB
- tests/validate.test.cjs 1 KB
- tests/fixtures/bad-duplicate-id.yaml 1 KB
- tests/fixtures/bad-object-without-purpose.yaml 1 KB
- tests/fixtures/bad-planned-no-reason.yaml 1 KB
- tests/fixtures/bad-sub-no-id.yaml 1 KB
- tests/fixtures/bad-weak-check.yaml 1 KB
- tests/fixtures/legacy-goals.yaml 1 KB
- tests/fixtures/valid.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie purpose-tree.
Migawka bazy z 13.11.2026 · wersja paczki 3a36cae65c90 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100purpose-sync
Pod koniec sesji pracy proponuje aktualizacje drzewa celów projektu, by realized_by odpowiadało temu, co robi kod, i wskazuje zmiany, które nie służą żadnemu celowi. - 100purpose-review
Buduje drzewo celów dla projektu, który go nie ma, albo przegląda istniejące: luki w całym drzewie, nieistniejące implementacje, nieaktualne węzły i nieprzechodzące kontrole. - 100yaml-master
Prawdopodobnie wspiera pracę z plikami YAML i aktywuje się automatycznie, gdy wykryje kontekst YAML. - 100yaml-master
Prawdopodobnie wspiera pracę z plikami YAML i aktywuje się automatycznie, gdy wykryje kontekst YAML. - 90Commit and push
Przegląda zmiany, dodaje tylko właściwe pliki, pisze commit po angielsku i wypycha go, gdy zasady projektu na to pozwalają. - 100factory-files
Tworzy i edytuje pliki definicji fabryki oprogramowania Warp w drzewie z factory.yaml: Agent, Automation, Scorer, Runner oraz drzewa skilli, i naprawia diagnostykę plików fabryki.