← ClaudeAtlas

cold-start-interviewlisted

Configure Tracework's knowledge vault, project identity, and reporting group for first use. Use for "/tracework:cold-start-interview", "configure Tracework", "set up Tracework", "初始化 Tracework", or "配置 Tracework".
KKenny0/Tracework · ★ 2 · Code & Development · score 65
Install: claude install-skill KKenny0/Tracework
# Tracework Cold Start Create the minimum configuration needed for scoped Daily, Weekly, Monthly, and Capture. Ask only for information that cannot be inferred safely. ## Required Result Global config: - `knowledge_vault` - optional `profile.default_reporting_group` Project config when inside a project: - `project_slug` - `profile.project_name` - `profile.reporting_group` Then register the project in `{vault}/raw/projects.json`, including `reporting_group`. ## Preflight 1. Detect the project root from `.git` or `.tracework`. 2. Read global and project configs when present. 3. Preserve all unknown and unrelated fields. 4. Stop early when the required fields above are complete. Do not re-ask existing values. Do not require report language, weekly mode, team context, artifact index, or session scanning during first setup. ## Interview Ask for all missing required values in one compact pass: 1. Knowledge vault absolute path. Ask before creating a missing directory. 2. Human project name when in a project. 3. Project slug, with a kebab-case suggestion from the repo name. 4. Reporting group for the project. Recommend `work` or `personal`, but accept another non-empty stable group such as `open-source` or `consulting`. 5. When the user has multiple groups, ask which should be the default report scope. Recommend `work` for audience safety. Reporting group is not cosmetic: it prevents personal projects from entering a workplace report. Never infer `work` from a pat