project-role-distributor

name	project-role-distributor
description	Reads any type of project requirement file (text, markdown, pdf, code structure, etc.), determines necessary roles for the project, and rigorously distributes tasks and responsibilities so that they are strictly equal across roles based on complexity points, estimated time, and total task count. Use this skill whenever a user provides a project file or asks you to "distribute tasks", "create roles", or "break down project work equally."
compatibility	null

Project Role & Task Distributor

When asked to determine roles and distribute work for a project, your goal is to rigorously balance responsibilities instead of superficially guessing at task sizes. You will analyze the provided input (such as a PRD, a raw transcript of requirements, technical specifications, or code structure), break the project into concrete tasks, and map them to appropriate roles to ensure a perfectly balanced workload for everyone on the team.

Step 1: Deep Analysis and Research

Read the provided project files or requirements thoroughly. You MUST act as a senior technical architect and product manager. If the requirements are brief or high-level, you MUST proactively search the internet (or use your internal knowledge base) to research the necessary technical and product components required to implement the requested features. Identify every explicit and implicit technical requirement (e.g., database schemas, API architecture, third-party integrations, authentication, infrastructure setup, security measures).

List all distinct tasks required to deliver the project.

For every task, explicitly estimate:

• Time to Complete (in hours or days)
• Complexity Points (1-8 Fibonacci points or a 1-10 difficulty scale)

Do not leave any implicit work behind—consider QA, deployment, documentation, and coordination.

Step 2: Define Roles

Based on the task breakdown, identify the necessary roles for the project. Example roles: Frontend Developer, Backend Developer, QA Engineer, Project Manager, DevOps Engineer. Explain briefly why each role is needed.

Step 3: Equal Distribution Algorithm

You MUST prove the fairness of the assignment. Assign the tasks to the identified roles such that the following metrics are as perfectly balanced as possible across all roles:

1. Total time estimate
2. Total complexity points
3. Total task count

If the workload does not split perfectly across specialized roles (for example, there is 80 hours of frontend work but only 20 hours of backend work), you must create "cross-functional" or "hybrid" roles, or redefine the roles (e.g. Developer A and Developer B) to guarantee an equal workload across the team members.

Output Format

Generate your output strictly in Markdown format as follows:

Project Task Distribution

1. Role Definitions

(List of roles and why they are necessary)

2. Master Task List

(A table listing all tasks, their complexity points, and time estimates)

Task	Complexity	Time Exp.
...	...	...

3. Equitable Distribution

(For each role, list the assigned tasks and the aggregated totals to PROVE equality)

[Role Name]

• Tasks:
  • [Task Name] (Complexity: X, Time: Y)
• Totals:
  • Tasks: [Sum]
  • Complexity Points: [Sum]
  • Estimated Time: [Sum]

4. Variance Check

(A brief table or summary showing the differences in totals between all roles. The variance should ideally be 0 or very close to it.)