Building a Comprehensive Programming Team

编程 ChatGPT 3分
收藏

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

使用建议

  1. 想直接看效果?在「变量填充 / 测试」里点「测试效果」,AI 会返回真实结果;满意再「复制结果」。存在「我的版本」时可分别测试、并排对比。
  2. 也可点「复制提示词」直接复制原文,手动替换占位符。
  3. 把内容粘贴到对应 AI 模型(ChatGPT)的对话框。
  4. 想改成自己的版本?切到「编辑我的版本」,保存私有版本或公开提交。

标签

相似提示词

同分类下其他优质提示词

查看全部 →

接手陌生仓库:理清项目结构与入口的地图

刚接手一个别人的项目,几千个文件不知从哪看起,越翻越乱。输入仓库概况,帮你理清入口、目录与依赖,先画出一张能上手的结构地图,不改代码。适合接手新项目的人。

复制 0 次

技术选型对比:多个候选方案按维度权衡

同一个需求有好几种做法,各说各有理,选完又担心选错。输入你的候选与约束,帮你搭一张按维度打分的权衡表,把取舍写下来便于日后回看。适合要做架构决策的人。

复制 0 次

口头需求转开发任务:拆解与验收标准

产品一句话需求就丢过来,做完发现理解偏了、也没标准验收。输入你收到的需求,帮你拆成可开发的任务并写清验收标准。适合要接需求动手的人。

复制 0 次

慢接口定位热点:分段计时找出耗时大头

一个接口越来越慢,笼统优化没头绪。输入耗时现象与处理流程,帮你设计分段计时把热点定位出来,再对症。适合被性能问题盯上的人。

复制 0 次

破坏性变更影响评估:一处改动会波及哪些调用方

改了个公共方法或数据结构,不知道有多少地方依赖它,上线才发现连锁报错。输入改动内容,帮你评估影响面、列出要同步的调用方与兼容策略。适合改共享代码的人。

复制 0 次

状态管理数据流梳理:把共享状态理清楚

页面状态散落在各处,一个值被谁改、改完谁受影响说不清,bug反复。输入你的状态情况,帮你把数据来源、流向与影响面梳理成图。适合被状态混乱困扰的前端。

复制 0 次
对比 /4
去对比 → 再选 1 个