# Teamwork Init

> Use when the user asks to add or refresh concise project-local Teamwork instructions in one named project; do not use to install global tools or create workflow records.

- Skill: `jinplu/teamwork-init` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jinplu/teamwork-init`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jinplu/teamwork-init/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: JinPLu (https://skillmd.com/u/jinplu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jinplu/teamwork-init

---


# Teamwork Init

Init adds one small managed block to the project's agent instruction file, plus
the small import bridge a host needs to read that block. It creates no document
database, schema, case directory, runtime state, or migration path.

## Method

1. Resolve a trustworthy Teamwork package source: read
   `~/.teamwork/install.json` `root`; use that path if it contains `VERSION`,
   `skills/`, and `install.sh`. If the pointer is missing or invalid, ask the
   user for the repository path. Do not search the home directory. Then resolve
   the authorized project root and read its instruction hierarchy.
2. Preserve all user-owned content outside the Teamwork managed markers.
3. Run `./install.sh --project-root <root> init-project` from that resolved
   package source.
4. Re-read the resulting project instruction surfaces and report each exact
   changed surface or the observed no-op.

The command is idempotent: an existing Teamwork block is refreshed in place, and
an instruction file that already reaches the block is left unchanged.
Ambiguous duplicate markers or an unreadable target are real file-ownership
conflicts; version, schema, readiness, and agent availability are not Init
preconditions.

Init never creates an empty `docs/teamwork` tree. Document directories appear only
when a Skill checkpoint asks Writer to write a file there. When Init observes
no change, report the observed no-op. Create or update a durable report only
when that result is reusable or the user explicitly requests it.

## Persistence

Persistence is optional. Write a report only when the observed result is reusable
across sessions or the user explicitly requests it. When that optional
checkpoint fires, write the document in the same response cycle from
`references/report.md` at
`docs/teamwork/reports/<slug>.md` (reuse the existing path for the
same project-operation identity). Optional triggers: Init completes with an
observed `AGENTS.md` change worth reusing; Init stops on a real file-ownership
conflict worth reusing; or a no-op result is reusable or explicitly requested.
Init never blocks on a report.