| name | context-setup |
| description | Build, import, or refresh this workspace's identity, project, reusable-workflow, and weekly-state files through a guided review. Use only when the user explicitly asks to initialize or redo workspace context. |
Set up workspace context
Build useful context from the user's own words or selected migration material without silently overwriting existing files.
Guardrails
- Ask questions one at a time.
- Inspect existing files before proposing changes. Treat non-placeholder content as user data.
- Preserve the user's wording; do not embellish credentials, goals, or biography.
- Show the proposed file map and summarize replacements before writing.
- Require approval before overwriting populated files, creating broad batches of files, committing, or pushing.
- Never request or store passwords, access tokens, recovery codes, or other credentials.
- Never ingest a raw account export or complete conversation archive into tracked context.
Procedure
1. Confirm storage and audience before collecting context
Explain that identity, project, state, session, and imported context can be
sensitive. Tracked files are visible to every repository collaborator and
configured agent, and deleting them later does not erase them from git history.
Recommend a local-only workspace or private remote by default; a public remote
requires deliberately sanitized content. Keep raw exports and migration staging
outside tracked files.
Ask the user to confirm that the current storage location, repository audience,
and intended agent access are appropriate. If they do not explicitly confirm,
stop before reading migration material or asking for personal information.
2. Choose the starting point
Ask whether the user wants to start from their answers, selected existing material, or both.
For existing material, read docs/migration-guide.md. Ask for one reviewed migration packet or a narrow set of source files. Inventory the selected input, mark claims that need verification, identify sensitive items that should stay out of the workspace, and propose destinations. Do not read beyond the scope the user selected.
