Junior Consultant Tasks
Marching orders for documentation and knowledge base work. Complete these tasks in order.
Phase 1: Inventory & Audit (Week 1-2)
Task 1.1: Project Discovery
Goal: Document every project in ~/dev
# Run this to find all projects
ls -la ~/dev | grep -v node_modules
# Find all package.json files
find ~/dev -maxdepth 2 -name "package.json" -type f 2>/dev/nullDeliverable: Create ~/dev/aicr/docs/inventory/projects.json
{
"projects": [
{
"name": "project-name",
"path": "~/dev/project-name",
"type": "app|package|service",
"hasClaudeMd": true,
"vercelConnected": true,
"port": 3000,
"description": "Brief description"
}
]
}Task 1.2: CLAUDE.md Audit
Goal: Ensure every project has a quality CLAUDE.md
For each project:
- Check if CLAUDE.md exists
- If yes, review for completeness
- If no, create one following template below
Template:
# [Project Name]
## What is this?
[One paragraph description]
## Architecture
[Key directories and their purposes]
## Key Files
- `file1.ts` - Purpose
- `file2.ts` - Purpose
## Commands
```bash
pnpm dev # Start development
pnpm test # Run tests
pnpm build # Build for productionEnvironment Variables
VAR_NAME- Description
Dependencies
- Depends on: [other projects]
- Used by: [projects that use this]
### Task 1.3: Environment Variable Mapping
**Goal**: Document all environment variables across projects
**Deliverable**: Create `~/dev/aicr/docs/inventory/env-vars.json`
```json
{
"variables": [
{
"name": "OPENAI_API_KEY",
"projects": ["aicr", "intelligentspm"],
"source": "vercel",
"required": true,
"description": "OpenAI API key for AI features"
}
]
}Phase 2: Documentation Content (Week 3-4)
Task 2.1: API Documentation
Goal: Document all API endpoints
For each API route:
- Find route files (
app/api/**/route.ts) - Document: method, path, request body, response
- Add to docs site
Location: ~/dev/aicr/apps/docs/pages/api-reference/
Task 2.2: Architecture Diagrams
Goal: Create visual documentation
Tools to use:
- Mermaid (built into docs site)
- ASCII diagrams for CLAUDE.md files
Required diagrams:
- Overall ecosystem architecture
- Data flow between projects
- AI request routing
- Database relationships
Task 2.3: Troubleshooting Guide
Goal: Document common issues and solutions
Deliverable: ~/dev/aicr/apps/docs/pages/guides/troubleshooting.mdx
Common issues to document:
- "Cannot connect to database"
- "API key not working"
- "Ollama not responding"
- "Vercel deployment failed"
- "CORS errors"
Phase 3: Knowledge Base (Week 5-6)
Task 3.1: Review SPM Knowledge Cards
Goal: Audit and improve knowledge base content
-
Review all 929 cards in:
~/dev/intelligentspm/src/data/spm-kb-cards.json -
For each card, check:
- Content accuracy
- Proper categorization
- Complete information
- Correct formatting
-
Document gaps in spreadsheet
Task 3.2: Add Missing Content
Goal: Fill gaps identified in audit
Categories to ensure coverage:
- Sales Performance Management fundamentals
- Incentive Compensation Management
- Sales Governance
- Territory Management
- Quota Management
- Commission calculations
Task 3.3: Embedding Quality Check
Goal: Ensure RAG system works correctly
- Test queries against AskSPM
- Document queries that return poor results
- Identify content gaps from failed queries
Progress Tracking
Create a daily log at ~/dev/aicr/docs/inventory/progress.md:
# Progress Log
## 2026-01-27
- [ ] Task 1.1: Found 20 projects
- [ ] Task 1.2: 5/20 CLAUDE.md files reviewed
- Notes: [observations]
## 2026-01-28
...Completion Criteria
Phase 1 Complete When:
- All projects documented in projects.json
- All projects have CLAUDE.md
- All env vars mapped
Phase 2 Complete When:
- All API endpoints documented
- Core architecture diagrams created
- Troubleshooting guide covers top 10 issues
Phase 3 Complete When:
- All 929 cards reviewed
- Gap analysis complete
- 10 test queries return quality results
Questions?
- Check existing docs first
- Use Claude Code with project CLAUDE.md
- Escalate blockers immediately
- Weekly sync with team lead