WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

CLAUDE MD Small Team

rUv edited this page Jul 30, 2025 · 2 revisions

Claude Code Configuration for Small Teams (2-5 Developers)

🚀 CRITICAL: Small Team Collaborative Parallel Execution

MANDATORY RULE: In small team environments, ALL development activities MUST be collaborative and efficiently coordinated:

  1. Team Planning → Initialize swarm with team scope in ONE call
  2. Feature Allocation → Batch ALL task assignments together
  3. Code Reviews → Parallel execution of all quality checks
  4. Team Sync → Batch ALL communication activities together

👥 SMALL TEAM SWARM ORCHESTRATION PATTERN

Team Project Initialization (Single Message)

[BatchTool - Small Team Setup]:
  // Initialize collaborative team swarm
  - mcp__claude-flow__swarm_init { 
      topology: "mesh", 
      maxAgents: 6, 
      strategy: "small_team_collaborative" 
    }
  
  // Spawn team-oriented agents
  - mcp__claude-flow__agent_spawn { type: "coordinator", name: "Team Lead" }
  - mcp__claude-flow__agent_spawn { type: "coder", name: "Frontend Specialist" }
  - mcp__claude-flow__agent_spawn { type: "coder", name: "Backend Specialist" }
  - mcp__claude-flow__agent_spawn { type: "tester", name: "QA Engineer" }
  - mcp__claude-flow__agent_spawn { type: "analyst", name: "Product Analyst" }
  - mcp__claude-flow__agent_spawn { type: "specialist", name: "DevOps Engineer" }

  // Small team todos - ALL collaborative aspects at once
  - TodoWrite { todos: [
      { id: "team-setup", content: "Establish team workflow and communication patterns", status: "completed", priority: "high" },
      { id: "role-definition", content: "Define team roles and responsibilities", status: "in_progress", priority: "high" },
      { id: "project-planning", content: "Break down project into team-sized tasks", status: "pending", priority: "high" },
      { id: "code-standards", content: "Establish coding standards and review process", status: "pending", priority: "high" },
      { id: "git-workflow", content: "Set up branching strategy and merge policies", status: "pending", priority: "high" },
      { id: "development-environment", content: "Standardize development environment across team", status: "pending", priority: "medium" },
      { id: "testing-strategy", content: "Define testing responsibilities and coverage", status: "pending", priority: "medium" },
      { id: "deployment-pipeline", content: "Set up collaborative deployment process", status: "pending", priority: "medium" },
      { id: "knowledge-sharing", content: "Establish documentation and knowledge sharing", status: "pending", priority: "low" },
      { id: "team-retrospectives", content: "Schedule regular team improvement sessions", status: "pending", priority: "low" }
    ]}

  // Initialize small team memory context
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "small_team/project_context", 
      value: { 
        team_size: 4,
        roles: ["team_lead", "frontend_dev", "backend_dev", "qa_engineer"],
        communication_style: "informal_but_structured",
        meeting_frequency: "daily_standups_weekly_planning",
        tech_stack: "react_node_mongodb_docker",
        deployment_frequency: "weekly_releases"
      } 
    }

🤝 TEAM COLLABORATION COORDINATION

Daily Team Communication

MANDATORY: Every team member MUST use coordination hooks for team sync:

# Daily team sync (each team member runs this)
npx claude-flow@alpha hooks pre-task --description "Daily team sync and task coordination" --auto-spawn-agents false
npx claude-flow@alpha hooks notify --message "Team member: [name], Today's work: [tasks], Blockers: [issues], Help needed: [requests]" --telemetry true

Small Team Agent Template

You are the [Team Role] in a small collaborative development team.

MANDATORY SMALL TEAM COORDINATION:
1. COMMUNICATION: Over-communicate progress and blockers
2. COLLABORATION: Work closely with other team members
3. FLEXIBILITY: Be ready to help in areas outside your specialty
4. QUALITY: Maintain high standards through peer review
5. KNOWLEDGE SHARING: Document and share learnings with the team

Your primary responsibility: [specific role and expertise]
Team dependencies: [other team members you work closely with]
Communication frequency: [daily updates, weekly deep dives]

REMEMBER: In a small team, everyone's contribution is critical to success!

💻 FEATURE DEVELOPMENT WITH PAIR PROGRAMMING

Collaborative Feature Implementation

// ✅ CORRECT: Small team collaborative feature development
[BatchTool - Collaborative Feature Development]:
  // Team members work on different aspects simultaneously
  - Task("Frontend Specialist: Build user interface with design system consistency")
  - Task("Backend Specialist: Implement API endpoints with proper validation and error handling")
  - Task("QA Engineer: Design test cases and set up automated testing")
  - Task("Team Lead: Review architecture decisions and coordinate integration")

  // Frontend development (pair programmed)
  - Write("src/components/UserDashboard.tsx", userDashboardCode)
  - Write("src/components/shared/LoadingSpinner.tsx", loadingSpinnerCode)
  - Write("src/hooks/useUserData.ts", userDataHookCode)
  - Write("src/styles/dashboard.module.css", dashboardStylesCode)

  // Backend development (reviewed by team lead)
  - Write("api/routes/users.js", userRoutesCode)
  - Write("api/controllers/userController.js", userControllerCode)
  - Write("api/middleware/validation.js", validationMiddlewareCode)
  - Write("api/models/User.js", userModelCode)

  // Testing suite (collaborative testing strategy)
  - Write("tests/frontend/UserDashboard.test.tsx", frontendTestCode)
  - Write("tests/backend/userRoutes.test.js", backendTestCode)
  - Write("tests/integration/userFlow.test.js", integrationTestCode)
  - Write("cypress/e2e/user-journey.cy.js", e2eTestCode)

  // Team documentation
  - Write("docs/feature-specifications/user-dashboard.md", featureSpecCode)
  - Write("docs/team-decisions/architecture-choices.md", architectureDocCode)
  - Write("CHANGELOG.md", changelogUpdateCode)

  // Store collaborative feature progress
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "small_team/features/user_dashboard", 
      value: { 
        status: "completed",
        contributors: ["frontend_specialist", "backend_specialist", "qa_engineer"],
        pair_programming_sessions: 3,
        code_review_iterations: 2,
        integration_challenges: ["state management", "api validation"]
      } 
    }

🔄 CODE REVIEW AND QUALITY PROCESS

Peer Review Workflow

[BatchTool - Code Review Process]:
  // Pull request templates and guidelines
  - Write(".github/pull_request_template.md", prTemplateCode)
  - Write(".github/ISSUE_TEMPLATE/bug_report.md", bugReportTemplateCode)
  - Write(".github/ISSUE_TEMPLATE/feature_request.md", featureRequestTemplateCode)

  // Code review automation
  - Write(".github/workflows/code-review.yml", codeReviewWorkflowCode)
  - Write("scripts/pre-commit-hooks.sh", preCommitHooksScript)
  - Write("scripts/lint-and-test.sh", lintTestScript)

  // Review guidelines
  - Write("docs/team-guidelines/code-review-checklist.md", codeReviewChecklistCode)
  - Write("docs/team-guidelines/coding-standards.md", codingStandardsCode)
  - Write("docs/team-guidelines/git-workflow.md", gitWorkflowCode)

  // Quality gates
  - Write("quality-gates/coverage-report.js", coverageReportCode)
  - Write("quality-gates/performance-budget.js", performanceBudgetCode)
  - Write("quality-gates/security-scan.js", securityScanCode)

Branching Strategy for Small Teams

# Feature branch creation with team coordination
npx claude-flow@alpha hooks pre-task --description "Creating feature branch for team collaboration"
git checkout -b feature/user-dashboard-team-collab
npx claude-flow@alpha hooks notify --message "Feature branch created: feature/user-dashboard-team-collab, Assigned to: [team members], Expected completion: [date]" --telemetry true

🎯 AGILE WORKFLOW FOR SMALL TEAMS

Sprint Planning and Execution

[BatchTool - Small Team Sprint]:
  // Sprint planning artifacts
  - Write("sprints/sprint-1/planning.md", sprintPlanningCode)
  - Write("sprints/sprint-1/backlog.md", sprintBacklogCode)
  - Write("sprints/sprint-1/capacity-planning.md", capacityPlanningCode)

  // Task distribution
  - Write("sprints/sprint-1/task-assignments.md", taskAssignmentsCode)
  - Write("sprints/sprint-1/dependencies.md", dependenciesCode)
  - Write("sprints/sprint-1/risks.md", risksCode)

  // Daily standup tracking
  - Write("sprints/sprint-1/standup-notes.md", standupNotesCode)
  - Write("sprints/sprint-1/burndown-chart.md", burndownChartCode)

  // Sprint retrospective
  - Write("sprints/sprint-1/retrospective.md", retrospectiveCode)
  - Write("sprints/sprint-1/action-items.md", actionItemsCode)

  // Store sprint metrics
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "small_team/sprint_1_metrics", 
      value: { 
        planned_story_points: 32,
        completed_story_points: 28,
        team_velocity: 28,
        blockers_encountered: 2,
        pair_programming_hours: 16,
        team_satisfaction: 4.2
      } 
    }

🛠️ TEAM DEVELOPMENT ENVIRONMENT

Standardized Development Setup

[BatchTool - Team Dev Environment]:
  // Docker development environment
  - Write("docker-compose.dev.yml", dockerDevComposeCode)
  - Write("Dockerfile.dev", dockerfileDevCode)
  - Write(".devcontainer/devcontainer.json", devContainerCode)

  // Team tooling configuration
  - Write(".vscode/settings.json", teamVSCodeSettingsCode)
  - Write(".vscode/extensions.json", teamVSCodeExtensionsCode)
  - Write("package.json", teamPackageJsonCode)

  // Environment setup scripts
  - Write("scripts/setup-dev-env.sh", devEnvSetupScript)
  - Write("scripts/install-dependencies.sh", dependenciesInstallScript)
  - Write("scripts/start-services.sh", startServicesScript)

  // Team documentation
  - Write("docs/team-setup/onboarding.md", onboardingGuideCode)
  - Write("docs/team-setup/development-workflow.md", devWorkflowCode)
  - Write("docs/team-setup/troubleshooting.md", troubleshootingGuideCode)

  // Shared utilities
  - Write("shared/utils/teamHelpers.js", teamHelpersCode)
  - Write("shared/config/teamConfig.js", teamConfigCode)
  - Write("shared/constants/teamConstants.js", teamConstantsCode)

📊 TEAM COMMUNICATION AND DOCUMENTATION

Knowledge Sharing System

[BatchTool - Knowledge Sharing]:
  // Team wiki and documentation
  - Write("wiki/README.md", teamWikiHomeCode)
  - Write("wiki/architecture-overview.md", architectureOverviewCode)
  - Write("wiki/coding-guidelines.md", codingGuidelinesCode)
  - Write("wiki/deployment-process.md", deploymentProcessCode)

  // Decision records
  - Write("decisions/001-frontend-framework-choice.md", frontendDecisionCode)
  - Write("decisions/002-database-selection.md", databaseDecisionCode)
  - Write("decisions/003-testing-strategy.md", testingDecisionCode)

  // Meeting notes and retrospectives
  - Write("meetings/weekly-sync/2024-01-15.md", weeklySyncNotesCode)
  - Write("meetings/retrospectives/sprint-1-retro.md", sprintRetroCode)
  - Write("meetings/technical-discussions/api-design-session.md", technicalDiscussionCode)

  // Team learning resources
  - Write("learning/team-skill-matrix.md", skillMatrixCode)
  - Write("learning/learning-goals.md", learningGoalsCode)
  - Write("learning/brown-bag-sessions.md", brownBagSessionsCode)

  // Store team knowledge
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "small_team/knowledge_base", 
      value: { 
        documentation_coverage: 85,
        decision_records: 12,
        team_learnings: ["react_patterns", "api_design", "testing_best_practices"],
        knowledge_sharing_frequency: "weekly",
        onboarding_time: "2_days"
      } 
    }

Communication Protocols

# Team communication coordination
npx claude-flow@alpha hooks notify --message "Team communication: [async/sync], Topic: [technical/planning/blocker], Participants: [team members]" --telemetry true

🚀 SMALL TEAM BEST PRACTICES

✅ DO:

  • Over-communicate: Share progress, blockers, and decisions openly
  • Pair Program: Collaborate on complex features and knowledge transfer
  • Cross-train: Everyone should understand multiple areas of the codebase
  • Regular Retrospectives: Continuously improve team processes
  • Shared Ownership: Everyone is responsible for code quality and project success
  • Flexible Roles: Be willing to help outside your primary expertise
  • Document Decisions: Keep track of architectural and technical decisions

❌ DON'T:

  • Don't work in silos - always coordinate with team members
  • Avoid knowledge hoarding - share learnings and discoveries
  • Don't skip code reviews even for small changes
  • Never deploy without team awareness and approval
  • Don't let technical debt accumulate without team discussion
  • Avoid individual hero programming - collaborate instead
  • Don't make major architectural decisions without team input

🔧 DEPLOYMENT AND OPERATIONS

Team Deployment Strategy

[BatchTool - Team Deployment]:
  // Deployment pipeline for small teams
  - Write(".github/workflows/team-deploy.yml", teamDeployWorkflowCode)
  - Write("scripts/deploy-staging.sh", stagingDeployScript)
  - Write("scripts/deploy-production.sh", productionDeployScript)

  // Environment management
  - Write("environments/development.env", devEnvironmentCode)
  - Write("environments/staging.env", stagingEnvironmentCode)
  - Write("environments/production.env", prodEnvironmentCode)

  // Monitoring and alerting
  - Write("monitoring/team-dashboard.json", teamDashboardCode)
  - Write("monitoring/alerts.yml", alertsConfigCode)
  - Write("scripts/health-check.sh", healthCheckScript)

  // Incident response
  - Write("ops/incident-response.md", incidentResponseCode)
  - Write("ops/rollback-procedure.md", rollbackProcedureCode)
  - Write("ops/team-on-call.md", onCallProcedureCode)

📈 TEAM PERFORMANCE AND METRICS

Team Productivity Tracking

// Team performance metrics
- mcp__claude-flow__memory_usage { 
    action: "store", 
    key: "small_team/performance_metrics", 
    value: { 
      team_velocity: 32,
      code_review_time: "4_hours_average",
      pair_programming_percentage: 40,
      bug_rate: "0.5_per_feature",
      deployment_frequency: "weekly",
      team_happiness_score: 4.3,
      knowledge_sharing_sessions: 2
    } 
  }

Continuous Improvement Process

# Weekly team improvement check
npx claude-flow@alpha hooks pre-task --description "Weekly team improvement session"
npx claude-flow@alpha hooks notify --message "Team improvements: [what worked well], [what to improve], [action items for next week]" --telemetry true

🎯 PROJECT TYPES FOR SMALL TEAMS

Startup MVP Development

[BatchTool - Startup MVP]:
  // MVP feature prioritization
  - Write("product/mvp-features.md", mvpFeaturesCode)
  - Write("product/user-stories.md", userStoriesCode)
  - Write("product/competitive-analysis.md", competitiveAnalysisCode)

  // Rapid development setup
  - Write("src/components/mvp/LandingPage.tsx", landingPageCode)
  - Write("src/components/mvp/UserOnboarding.tsx", onboardingCode)
  - Write("src/components/mvp/CoreFeature.tsx", coreFeatureCode)

  // Analytics and feedback
  - Write("analytics/user-tracking.js", userTrackingCode)
  - Write("feedback/user-feedback-system.js", feedbackSystemCode)

Client Project Delivery

[BatchTool - Client Project]:
  // Client communication
  - Write("client/project-proposal.md", projectProposalCode)
  - Write("client/progress-reports.md", progressReportsCode)
  - Write("client/delivery-checklist.md", deliveryChecklistCode)

  // Quality assurance
  - Write("qa/client-acceptance-tests.js", clientAcceptanceTestsCode)
  - Write("qa/performance-benchmarks.js", performanceBenchmarksCode)
  - Write("qa/security-checklist.md", securityChecklistCode)

Open Source Collaboration

[BatchTool - Open Source Project]:
  // Community management
  - Write("community/contributor-guidelines.md", contributorGuidelinesCode)
  - Write("community/code-of-conduct.md", codeOfConductCode)
  - Write("community/issue-templates.md", issueTemplatesCode)

  // Release management
  - Write("releases/release-process.md", releaseProcessCode)
  - Write("releases/changelog-template.md", changelogTemplateCode)
  - Write("releases/version-strategy.md", versionStrategyCode)

💡 TEAM SCALING CONSIDERATIONS

Preparing for Growth

[BatchTool - Team Scaling Prep]:
  // Process documentation for scaling
  - Write("scaling/team-growth-plan.md", teamGrowthPlanCode)
  - Write("scaling/onboarding-process.md", onboardingProcessCode)
  - Write("scaling/knowledge-transfer.md", knowledgeTransferCode)

  // Architecture for scaling
  - Write("architecture/modularity-guidelines.md", modularityGuidelinesCode)
  - Write("architecture/microservices-preparation.md", microservicesCode)
  - Write("architecture/testing-at-scale.md", testingAtScaleCode)

  // Tool and process evolution
  - Write("tools/team-tool-evaluation.md", toolEvaluationCode)
  - Write("processes/workflow-optimization.md", workflowOptimizationCode)

Knowledge Preservation

# Team knowledge preservation
npx claude-flow@alpha hooks post-task --task-id "knowledge_documentation" --analyze-performance true
npx claude-flow@alpha hooks notify --message "Knowledge documented: [technical decisions], [lessons learned], [best practices discovered]" --telemetry true

Remember: Small teams thrive on collaboration, communication, and shared ownership. Claude Flow enhances small team dynamics by providing intelligent coordination that maintains the intimacy and agility of small teams while ensuring professional development practices!

Clone this wiki locally