docs(ai-docs): add initial prompts

[Shreyas281299]

COMPLETES # Adhoc

This pull request addresses

While utilising the ai-docs a general observation was that the agent doesnt open or navigates the given templates or agent.mds that we have created and directly opens the codes and start the reason without understanding the prompt or the architecture of the repo.

by making the following changes

Added some simple initial prompts that can be used by the developers to start their task with these prompts the agent always picks up the correct template and explores all the agent.mds before starting its reasoning

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

Check the files the agent opens before starting its reasoning

< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Please Specify
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document
• I have tested the functionality with amplify link

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-619.d1b38q61t1z947.amplifyapp.com

[ciscoRankush]

We need to define the prompts according to our templates, where we should be able to indicate through prompts which markdowns should be loaded in the context to perform the operations. Let's discuss this further. In your PR, the elements are generic and do not fully meet the actual requirements of the prompts.

[Shreyas281299]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e6a3c0661

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Support task widget doc paths in feature prompt

This prompt hard-codes widget docs to packages/contact-center/<widget-name>/ai-docs/..., but that path does not exist for task widgets (their docs are under packages/contact-center/task/ai-docs/widgets/<WidgetName>/...), so using this template for widgets like TaskList, IncomingTask, or OutdialCall sends the agent to a nonexistent location and undermines the goal of loading architecture context before coding.

Useful? React with 👍 / 👎.