+ It covers the requirements clearly and evenly.
- Most KPIs lack targets and measurement periods.
--- name: building-a-comprehensive-programming-team description: Create a programming team with defined roles: team brain, task distributor, programme
| Category | Development › Technical writing |
|---|---|
| Tags | DraftingOffice workerDeveloperTemplate |
--- name: building-a-comprehensive-programming-team description: Create a programming team with defined roles: team brain, task distributor, programmer, and manager, ensuring a well-rounded and effective development process. --- Act as a Team Builder. You are tasked with creating a comprehensive programming team consisting of five key roles to ensure an effective development process. Your team will include: 1. **Team Brain** - Responsible for strategic thinking and innovation. 2. **Task Distributor** - Manages and allocates tasks among team members efficiently. 3. **Programmer** - Handles coding and software development tasks. 4. **Manager** - Oversees project timelines and ensures team collaboration. Your task is to: - Define clear responsibilities for each role. - Ensure effective communication and collaboration within the team. - Facilitate a balanced workload and maintain team motivation. Team Needs: - **Strong Communication Skills**: To ensure effective communication among team members. - **Project Management Tools**: Such as Jira or Trello for tracking progress and managing tasks. - **Shared Work Environment**: Like Slack or Microsoft Teams to facilitate collaboration. - **Specialized Technical Skills**: Depending on the project area like programming, design, or quality testing. - **Effective Leadership**: To guide the team towards common goals. - **Continuous Learning Culture**: To adopt new technologies and improve skills. - **Clear Role and Responsibility Definition**: To ensure clarity of goals and avoid task overlap. Rules: - Each role must have specific objectives and KPIs. - Regular team meetings to synchronize efforts and track progress. - Encourage continuous learning and adaptation to new technologies. FILE:README.md
Useful for documenting development-team roles and operating rules. The text mentions five roles, but the visible list mainly shows four, and it appears targeted at README.md.
ChatGPT offers the best balance of accuracy, completeness, and length. Gemini is more detailed but has flawed KPIs, while Claude invents execution history and omits the full deliverable.
+ It covers the requirements clearly and evenly.
- Most KPIs lack targets and measurement periods.
+ Roles, objectives, and KPIs are highly concrete.
- Some targets are unrealistic, and eNPS is mis-scaled.
+ It clearly resolves the missing fifth-role issue.
- It invents file writes and shell-command history.
| Criterion | ChatGPT | Claude | Gemini | Leader |
|---|---|---|---|---|
| Instruction following | 9 | 5 | 9 | Tie |
| Accuracy | 9 | 4 | 7 | ChatGPT +29% |
| Specificity | 8 | 6 | 9 | Gemini +13% |
| Structure | 9 | 7 | 9 | Tie |
| Right length | 9 | 5 | 8 | ChatGPT +13% |
Scored 1–10 by gpt-5.6-sol with model names hidden (2026-09-24). This is an AI review, not a measurement.
We gave three models the same input and copied their answers unedited. Each ran in its CLI (an agent harness), and answers in the ChatGPT or Claude apps or on the web may differ. Outputs are in Korean.
효율적인 개발을 위해 전략, 업무 배분, 구현, 품질 관리, 프로젝트 운영을 담당하는 5개 역할로 팀을 구성합니다.
| 역할 | 주요 책임 |
|---|---|
| 팀 브레인 | 제품 방향과 기술 전략 수립, 문제 해결, 혁신 아이디어 제안 |
| 업무 분배자 | 업무를 세분화하고 우선순위와 담당자를 배정하며 진행 상황 관리 |
| 프로그래머 | 기능 설계, 코드 작성, 리팩터링, 기술 문서화 |
| 품질 엔지니어 | 테스트 계획 수립, 버그 검증, 품질 기준 및 배포 안정성 관리 |
| 매니저 | 일정, 리스크, 협업, 자원 및 팀 성과 관리 |
목표
KPI
목표
KPI
목표
KPI
목표
KPI
목표
KPI
이 구조를 통해 팀 브레인은 방향을 제시하고, 업무 분배자는 실행을 조율하며, 프로그래머와 품질 엔지니어는 제품을 구현·검증하고, 매니저는 전체 프로젝트가 목표에 맞게 진행되도록 지원합니다.
| Act as an FTTH Telecommunications Expert | |
| Architect Guide for Programmers | |
| Beginner's Guide to Building and Deploying LLMs | |
| CLAUDE.md Assembly | |
| CLAUDE.md Generator for AI Coding Agents |