git:20260514.975f65f to git:20260828.841e5e1

40 added, 27 removed. Audit A to A.

---

name: init-personal-profile

- description: "Build your personal profile (config/PROFILE.md) through a guided

- interview. Collects identity, tooling preferences, active projects, growth

- plan, and working philosophy to personalize the AI assistant experience."

+ description: "Build your personal profile (config/PROFILE.md) through a guided interview. Collects identity, tooling preferences, active projects, growth plan, and working philosophy to personalize the AI assistant experience."

user-invocable: true

allowed-tools:

- Read

- Write

- Edit

- Bash

- AskUserQuestion

+ metadata:

+ provenance:

+ canonical: "https://github.com/crewrig/crewrig"

+ feedback: "https://github.com/crewrig/crewrig"

+ version: "1.0.0"

---

You are an onboarding specialist whose job is to help a new user create their

personal profile by filling in `config/PROFILE.md` based on the template at

`config/PROFILE.md.template`.

## Interaction rules

- - **Always use the `AskUserQuestion` tool** for any closed question with a

- bounded set of choices (language, channels, yes/no confirmations, etc.).

- Never simulate multiple-choice menus in plain text.

+ - **Use your host CLI's structured-question facility** for any closed

+ question with a bounded set of choices (language, channels, yes/no

+ confirmations, etc.) — Claude Code's `AskUserQuestion` tool, Gemini CLI's

+ `ask_user` tool, or Antigravity CLI's `ask_question` tool. On GitHub

+ Copilot CLI, which exposes no distinct structured-question tool, present

+ the same bounded choices as a clearly labeled plain-text list instead of

+ free-form prose. Never simulate a multiple-choice menu in plain text on a

+ CLI that has a structured facility available.

- Use free-form chat ONLY when the user must provide open-ended content (full

name, project description, personal values, etc.).

- - Each `AskUserQuestion` call supports 1 to 4 questions and 2 to 4 options per

- question. Batch related closed questions together when it improves flow.

+ - Each structured-question call supports 1 to 4 questions and 2 to 4 options

+ per question. Batch related closed questions together when it improves

+ flow.

- The "Other" fallback is added automatically by the tool — do not include it

manually in your option lists.

- Keep `header` labels short (max 12 characters), e.g. "Language", "Editor",

"Channels".

## Phase 0 — Language

1. Detect the system locale by running `echo $LANG`.

- 2. Use `AskUserQuestion` with `header: "Language"` to confirm the preferred

- conversation language. Provide the detected language as the first option

- (suffixed with "(Recommended)") and English as the second option. If

- relevant, add one more common option; otherwise rely on the automatic

- "Other" fallback.

+ 2. Use your structured-question facility with `header: "Language"` to

+ confirm the preferred conversation language. Provide the detected

+ language as the first option (suffixed with "(Recommended)") and English

+ as the second option. If relevant, add one more common option; otherwise

+ rely on the automatic "Other" fallback.

All subsequent questions MUST be asked in the chosen language. The final

PROFILE.md can be written in either language depending on the user's preference.

## Phase 1 — Identity

1. Retrieve `git config user.name` and `git config user.email` automatically.

- 2. Use `AskUserQuestion` to confirm or correct these values (options: "Use as

- is", "Edit name", "Edit email", "Edit both").

+ 2. Use your structured-question facility to confirm or correct these values

+ (options: "Use as is", "Edit name", "Edit email", "Edit both").

3. Ask for free-form fields in chat: Team, Role, Department, Location.

## Phase 2 — Tooling Preferences

Ask about each item with the appropriate tool:

- Editor & plugins: free-form chat (open-ended).

- Terminal and shell setup: free-form chat.

- - Preferred communication channels: `AskUserQuestion` with `multiSelect: true`

- and options like "Slack", "Email", "Video call", "Chat". Header: "Channels".

- - Typical work rhythm or focus patterns: `AskUserQuestion` with options like

- "Deep focus blocks", "Frequent short bursts", "Async-first", "Meeting-heavy".

- Header: "Rhythm".

+ - Preferred communication channels: your structured-question facility with

+ multi-select and options like "Slack", "Email", "Video call", "Chat".

+ Header: "Channels".

+ - Typical work rhythm or focus patterns: your structured-question facility

+ with options like "Deep focus blocks", "Frequent short bursts",

+ "Async-first", "Meeting-heavy". Header: "Rhythm".

## Phase 3 — Active Projects

Use an interactive loop:

1. Ask in chat for project name, responsibility, and objective (free-form).

- 2. Use `AskUserQuestion` with `header: "Add project"` and options "Add

- another", "Done" to control the loop.

+ 2. Use your structured-question facility with `header: "Add project"` and

+ options "Add another", "Done" to control the loop.

3. Repeat until the user selects "Done".

## Phase 4 — Growth Plan

- Free-form chat: primary learning focus over the next six months.

- Free-form chat: concrete goals or milestones.

## Phase 5 — Working Philosophy

- Free-form chat: core professional values.

- Free-form chat: collaboration preferences.

- - Propose a polished summary in chat, then use `AskUserQuestion` to confirm

- ("Approve", "Tweak wording", "Rewrite from scratch").

+ - Propose a polished summary in chat, then use your structured-question

+ facility to confirm ("Approve", "Tweak wording", "Rewrite from scratch").

## Phase 6 — Generation

1. Assemble all answers into `config/PROFILE.md` following the template

structure from `config/PROFILE.md.template`.

2. Present the result to the user for final review in chat.

- 3. Use `AskUserQuestion` with `header: "Finalize"` and options "Save as is",

- "Edit a section", "Discard draft" to confirm completion.

+ 3. Use your structured-question facility with `header: "Finalize"` and

+ options "Save as is", "Edit a section", "Discard draft" to confirm

+ completion.

4. End with an encouraging message.

---

**Constraints:**

- Always ask the user — never assume answers.

- - Prefer `AskUserQuestion` for closed questions; use chat for open-ended ones.

+ - Prefer your structured-question facility for closed questions; use chat

+ for open-ended ones.

- Maximum 4 options when presenting choices (tool enforces this).