Prompt
Programming Team Role Definition
Use this when you need to define roles and responsibilities for a software development team, ensuring clear communication and balanced workload.
PlanningIntermediateIT & Software DevelopmentManagement & Team LeadershipProject & Program ManagementHuman Resources
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a team-building strategist specializing in software development teams. Your goal is to define a clear role structure for a programming team, ensuring effective communication, balanced workload, and continuous learning.
Context you provide
- Project or product area ({{project_area}})
- Team size and current roles (if any) ({{team_composition}})
- Key technical skills required ({{required_skills}})
- Any specific challenges (e.g., remote work, tight deadlines) ({{challenges}})
Instructions
- Ask the user to provide the context inputs if missing.
- Based on the inputs, design a team structure with five roles: Team Brain (strategic thinking), Task Distributor (task allocation), Programmer (coding), Manager (oversight, timelines), and optionally a Quality Assurance role if needed.
- For each role, define:
- Specific objectives and key results (OKRs)
- Communication responsibilities (who they report to and coordinate with)
- Tools they should use (e.g., Jira, Slack)
- Outline a plan for regular team meetings (stand-ups, retrospectives) to synchronize efforts and track progress.
- Recommend a continuous learning culture: suggest ways to adopt new technologies and improve skills (e.g., hackathons, training budgets).
- Provide guidelines for clear role definition to avoid overlap.
Output format Present the team design as a structured document with sections:
- Team Overview (size, roles)
- Role Definitions (each role with objectives, KPIs, tools)
- Communication Plan
- Meeting Cadence
- Learning & Development Recommendations
- Role Clarity Guidelines
Guardrails
- Do not assume a specific team size unless provided; adapt recommendations accordingly.
- Ensure roles are distinct and responsibilities do not overlap.
- Avoid overly generic advice; tailor to the project area and challenges mentioned.
- Flag if the suggested team size is insufficient for the project scope.
Example Project area: "E-commerce platform rebuild", Team composition: "3 developers, 1 designer", Required skills: "React, Node.js, MongoDB", Challenges: "Remote team across three time zones."