tmr-myself-config

tmr-myself-config

Conducts an adaptive conversation to build a complete picture of who you are as a manager — your working style, products, team, and collaborators — then writes that context across your vault so every AI skill becomes more assertive and personalized.

Usage

• /tmr-myself-config — full setup (first run or re-run; always merges, never overwrites)
• /tmr-myself-config update — delta review: checks current context against your vault, asks only what changed

---

EXECUTION

When invoked, check if the user passed the argument update. If so, follow the UPDATE section. Otherwise follow BOOTSTRAP → ARCHETYPE → BASE-CONTEXT → PRODUCT-BRANCH (if applicable) → PEOPLE-BRANCH (if applicable) → CONTRACTOR-CHECK → CONFIRM → WRITE in order.

---

BOOTSTRAP

Step B1: Locate the vault root

Run:

git rev-parse --show-toplevel

Store as VAULT_ROOT. All paths below are relative to VAULT_ROOT.

Step B2: Find the manager's profile

List all .md files in my-career/ (non-recursive). The file matching <email>.md (containing an @) is the manager's profile.

If none found: print "No profile found in my-career/. Run tmr init first." and exit. If multiple found: print the list and ask "Which is your profile?" Wait for the user's selection.

Store as PROFILE_PATH and MANAGER_EMAIL.

Read the profile frontmatter. Extract any already-known fields:

• name, role, company, manager_type, working_style, ai_communication_style

Store as KNOWN map. Fields present in KNOWN will not be re-asked unless the user requests it.

When loading direct reports in Step B3, read the relationship field from each profile. If relationship is absent (profile predates this schema), treat it as direct-report — the folder location is the authoritative fallback.

Step B3: Read existing vault context

Read and store (silently — no output to user yet):

1. Leadership: list files in my-leadership/. For each <email>.md, extract name, role.
2. Direct reports: list all <email>.md files in my-teams/members/. For each, extract name, role, relationship. If relationship is absent, default to direct-report.
3. Contractors: list all <email>.md files in my-company/contractors/members/. For each, extract name, role, company, relationship. If relationship is absent, default to contractor.
4. Collaborators: list all <email>.md files in my-company/members/. For each, extract name, role, relationship. Exclude entries where relationship: unknown — those are auto-created attendee profiles, not known collaborators.
5. Projects: list all subdirectory names in my-company/projects/. For each, read <slug>/<slug>-project.md frontmatter and extract name, status, owner. If no project file exists for a subdirectory, record status: unknown.
6. Org config: if config/organization.yaml exists, read internal_domains list. If it does not exist, INTERNAL_DOMAINS = [domain portion of MANAGER_EMAIL].