Setup Command

# Setup Command

## Command: `setup`

Initialize and configure this Context repository.

### Steps

1. **Run setup script**
   ```bash
   .context/scripts/setup.sh
   ```

2. **Explain Context**
   
   Give the user a brief overview:
   
   > **Welcome to Context** — a structured knowledgebase for your organization.
   > 
   > **One repo per org** — Each company, department, or team gets their own Context repo.
   > 
   > **Structure:**
   > - `/projects/` — Track multiple projects: ideas, progress updates, documentation
   > - `/people/` — Team member profiles organized by team, tracking focus, wins, and interests
   > - `/GLOSSARY.md` — Shared terminology for your domain
   > 
   > **What you can track:**
   > - Project progress (monthly updates with contributor attribution)
   > - Ideas and brainstorms per project
   > - People's current work, upcoming tasks, wins, and interests
   > - Cross-linking between people and projects
   > 
   > All folders have README.md files for easy navigation.
   
   Ask: "Ready to set up your Context repo? (yes/skip)"

3. **Configure README.md home page**
   
   Ask the user:
   - "What is the name of your company, department, or group?"
   - "Give a brief overview (1-2 sentences)."
   
   Replace `/README.md` with a branded home page containing:
   - The name as an H1 heading
   - The overview
   - A "Projects" section linking to `/projects/README.md`
   - A "People" section linking to `/people/README.md`
   - A "Glossary" section linking to `/GLOSSARY.md`
   
   Create `/projects/README.md` and `/people/README.md` with placeholder content.
   
   Example prompt: *"What's the name? (e.g., 'Acme Engineering', 'Platform Team')"*
   
   User can say "skip" to keep defaults.

4. **Populate GLOSSARY.md**
   
   Suggest 3-5 terms based on what you learned (domain, team name, industry).
   
   Ask: "Add any terms to the glossary? (e.g., 'API - Application Programming Interface')"
   
   Format: `**Term** - Definition`
   
   User can say "skip" or "done".

5. **Add people**
   
   Ask: "List some team members? (e.g., 'Sarah Chen, Platform, Senior Engineer')"
   
   For each person, create `/people/:team/:name.md` using the person file format from RULE.md.
   
   Update `/people/README.md` and any team README files.
   
   User can say "skip" or "done".

6. **Add projects**
   
   Ask: "Any projects to add? (e.g., 'API Gateway - Migrating to new gateway')"
   
   For each project:
   - Create `/projects/:project_name/README.md`
   - Create `/projects/:project_name/ideas.md` (empty or with initial ideas)
   - Create `/projects/:project_name/progress/` structure
   
   Update `/projects/README.md` with links.
   
   User can say "skip" or "done".

7. **Next steps**
   
   Remind the user:
   
   > **You're all set!** Here's what you can do next:
   > 
   > **Commands:**
   > - `ingest` — Add knowledge from documents, meeting notes, or other sources
   > - `setup` — Run this setup again anytime
   > 
   > **Tips:**
   > - Use `ingest` to pull in existing docs, Slack threads, or meeting notes
   > - Ask questions like "What is Sarah working on?" or "Show me API Gateway progress"
   > - Update people's wins and interests as you learn about them
   > 
   > Your Context repo grows more useful over time. Start with `ingest` to add more knowledge!

### Guidelines

- Be very concise in prompts
- Always allow "skip" to move on
- Provide domain-specific examples based on context gathered
- Placeholders are fine — the goal is a working structure
- After each step, briefly confirm what was created