Prompt chains for auto-prioritizing dev work

To create a prompt chain for auto-prioritizing development work, we can design a system that asks a series of questions in order to evaluate the relative importance and urgency of tasks. This can be used to automate the prioritization process for developers working on multiple projects or tasks.

Here’s a series of prompts that can guide the decision-making process:

Step 1: Assess Task Urgency

• Prompt 1: “Is this task time-sensitive or dependent on a specific deadline?”
  (Yes/No)
  If Yes, ask:
  “What is the deadline or time frame for this task?”

• Prompt 2: “Does this task directly impact a customer or user-facing feature?”
  (Yes/No)
  If Yes, ask:
  “How critical is this to the user experience? Can it be postponed or is it a blocker?”

Step 2: Evaluate Impact on the Product

• Prompt 3: “Will completing this task significantly improve product performance or stability?”
  (Yes/No)
  If Yes, ask:
  “On a scale from 1 to 10, how significant is the improvement?”

• Prompt 4: “Does this task address a known bug or issue affecting users?”
  (Yes/No)
  If Yes, ask:
  “How severe is the bug? Is it causing major disruptions or is it a minor issue?”

Step 3: Align with Business Goals

• Prompt 5: “Does this task contribute to a key business goal or objective?”
  (Yes/No)
  If Yes, ask:
  “How directly does it support this goal? Is it a critical path task?”

Step 4: Dependencies and Team Collaboration

• Prompt 6: “Is this task blocked by another task or dependent on the completion of other tasks?”
  (Yes/No)
  If Yes, ask:
  “Can the blocking task be expedited or worked around?”

• Prompt 7: “Does this task require collaboration with other teams or external resources?”
  (Yes/No)
  If Yes, ask:
  “What is the expected turnaround time from the other team or resource?”

Step 5: Resource Availability

• Prompt 8: “Do you have the necessary resources or team members available to complete this task?”
  (Yes/No)
  If No, ask:
  “When are the necessary resources available? Can this be rescheduled accordingly?”

Step 6: Estimate Workload

• Prompt 9: “How long will it take to complete this task?”
  (Provide estimated time in hours or days)

• Prompt 10: “What is the complexity of this task? On a scale from 1 to 5, how complex is it?”
  (Scale of 1 to 5)

Step 7: Risk Assessment

• Prompt 11: “Are there any potential risks or consequences if this task is delayed?”
  (Yes/No)
  If Yes, ask:
  “What are the risks, and how critical are they?”

Step 8: Final Prioritization Calculation

• After gathering all the information, the system can use the responses to calculate priority, such as:

  • Urgency (High/Medium/Low)

  • Impact (High/Medium/Low)

  • Dependencies (Blocking/Blocked)

  • Resources (Available/Not Available)

  • Risk (High/Medium/Low)

The task will be prioritized based on these factors, with a scoring mechanism that weights the most critical elements more heavily (e.g., Urgency and Impact might carry more weight).

Would you like help turning this into a more automated system, or do you have specific scenarios you’d like to test?