Reusable Prompts

[gcapnias]

The concept of having a library of pre-designed and well-tested prompts is really intriguing. Notably, some prompts in the library are interconnected, where the output of one serve as the input for another. Adding a scenario file, similar to a README.md file, could be a fantastic way to provide users with clear instructions on effectively using these linked prompts.

George J.

[aaronpowell]

Which ones have you noticed are interconnected? We've been trying to avoid that as it does make things more complex

[gcapnias]

Hi,

If you check Epic Product Requirements Document (PRD) Prompt and Epic Architecture Specification Prompt, you will see that the later actually should be using the output of the first to initialize its context.

To be honest, the whole commit is pure gold — having some instructions or examples would make it easier for everyone to see the value of these prompts and understand how to use them.

George J.

[danieldekay]

There are a few that are interconnected:

task-planner and task-researcher (with task-implementer also being by microsoft/edge-ai, and i don't know if that works with the others: but it requires the output of these two.)

then there are more, e.g. the breakdown-* family, which all store plans into /docs/ways-of-working

There is a PR to make prompt collections, which is great idea, as they could have their own README.md