init-team
Creates a new team file under config/teams/ through a guided interview and a bundled scaffold script that derives the filename and refuses to overwrite. Use when an adopter wants a per-team context and configuration profile, adds a team to config/teams, or types /init-team. Trigger terms: new team file, team profile, config/teams, team context, init team. Not for expertise or role profiles (init-expertise) or personal profiles.
- License 许可
- Apache-2.0
- 所属仓库
- crewrig/crewrig
- 最近更新
- 2026-11-15
- Stars
- ★ 24
- Forks
- 6
01 前言 Front Matter
- name
- init-team
- license
- Apache-2.0
- metadata
- { "provenance": { "version": "2.0.0", "feedback": "https://github.com/crewrig/crewrig", "canonical": "https://github.com/crewrig/crewrig" } }
- description
- Creates a new team file under config/teams/ through a guided interview and a bundled scaffold script that derives the filename and refuses to overwrite. Use when an adopter wants a per-team context and configuration profile, adds a team to config/teams, or types /init-team. Trigger terms: new team file, team profile, config/teams, team context, init team. Not for expertise or role profiles (init-expertise) or personal profiles.
- compatibility
- Requires Node.js 24 (scripts run as node scripts/<name>.ts) and a host CLI with a structured-question tool (AskUserQuestion on Claude Code). Writes one Markdown file under config/.
02 资源文件 2
- 脚本scripts/lint-config-file.ts8.8 KB
- 脚本scripts/scaffold-config-file.ts18.3 KB
03 SKILL.md 正文
Init Team
Creates one file, config/teams/<NAME>.md, in the catalog shape of config/teams/FORGE.md. You
run the interview, which is judgement; the scripts derive the filename, refuse to clobber, render
and check the file. The file is the organization's own, so upstream sync never touches it.
Interview rules
- Closed questions with a bounded set of choices go through
AskUserQuestion(optional-section choice, collision decision, confirmation); a plain-text menu gets skipped or misread. - Open content (mission, stack items, practices, contacts) is free-form chat.
- Talk in the user's language. The file is written in English, so translate the answers faithfully and add nothing the user did not say: an invented stack or practice would be read as the team's own.
- Keep
headerlabels under 12 characters.
Steps
- Name. Ask for the team name (for example "Atlas"). Run the resolve command; confirm
config/teams/<data.file>with the user. - Collision. If
data.existsis true, ask withAskUserQuestion(header: "Exists"): "Pick a different name" (back to step 1), "Overwrite the existing file", "Cancel" (stop, write nothing). Overwriting is a decision the user takes, never a default. - Core content, in chat: a short tagline; the mission (one paragraph: what the team builds
or operates and its north star); the technology stack (labeled bullets such as
**Language:** Java 21); 3 to 5 concrete development practices. - Optional sections.
AskUserQuestion(header: "Sections",multiSelect: true): Rituals, Collaboration Norms, Documentation, Issue Tracking, Key Contacts. Collect each selected one in chat. Rituals is a paragraph, the others are bullet lists. - Draft. Write the answers JSON to a scratch file, run the dry-run command and show
data.content. Ask withAskUserQuestion(header: "Finalize"): "Save as is", "Edit a section" (back to the relevant step), "Discard draft". - Save and check. Run the save command, then the linter. End with one line: the file is the organization's own and upstream sync will not touch it.
Scripts
Run node scripts/<name>.ts from the skill directory; paths you pass stay relative to the
repository root. Both scripts take --json and exit 0 (ok), 1 (finding), 2 (usage error) or
3 (precondition failed: unreadable input, --root not a directory).
| When | Command | Exit 1 means |
|---|---|---|
| After the name is known, and again after any rename | node scripts/scaffold-config-file.ts --kind team --name "<team name>" --json |
Never used here. Read data.file and data.exists. |
| To show the draft, then to save it | node scripts/scaffold-config-file.ts --kind team --answers <answers.json> --dry-run (draft in data.content), then the same without --dry-run |
target-exists: the file exists and was not written. Any other rule names an answers field to fix. |
| After saving | node scripts/lint-config-file.ts --kind team <path> |
A section is missing, out of order, empty or still a placeholder. Fix the answers and write again with --force, which is allowed here because this run created the file. |
Add --force to the save command only after the user has chosen to overwrite. Add --root <dir>
when the repository root is not the current directory. The answers file is JSON; the field list is
in node scripts/scaffold-config-file.ts --help.
04 同仓库更多 Skills
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.
fixture
Fixture skill. Mentions scripts/frontmatter-only.ts which must be ignored.