Add ADS Jira-to-PR agent workflow

[Aryanag2]

Jira

• Ticket: N/A

What Changed

• Added a repo-level AGENTS.md contract for a Jira ticket -> code -> unit tests -> PR workflow.
• Added docs/jira-ticket-template.md so the agent can validate whether a Jira issue is implementation-ready.
• Added .github/pull_request_template.md to standardize Jira linkage, validation notes, risks, and signoff checks.
• Moved the entire repository skill catalog from skills/ to .agents/skills/ so coding agents can find repo-local skills in one place.
• Added .agents/README.md as the entrypoint for the consolidated agent workspace.
• Added .agents/examples/jira-ticket-to-pr.md with an explicit Codex usage flow and prompt examples.

How To Use In Codex

1. Start Codex from the ADS repository root.
2. Read the root AGENTS.md and then select the smallest relevant skill under .agents/skills/.
3. For Jira-driven implementation, ask Codex to use jira-ticket-to-pr with a Jira key such as ADS-12345.
4. Codex validates the ticket against docs/jira-ticket-template.md, implements the change, updates unit tests, runs focused validation, and opens the PR if validation passes.
5. For follow-up work, use gh-pr-workflow, gh-address-comments, or gh-fix-ci depending on whether you want PR inspection, review-comment handling, or CI debugging.
6. See .agents/examples/jira-ticket-to-pr.md for example prompts and stop conditions.

Validation

• Manual review of the new workflow files and repo conventions.
• No code tests run; this change only adds agent workflow and documentation files.

Risks / Follow-Ups

• The workflow currently allows PR creation without requiring a new or modified unit test file; that can be tightened in a follow-up if needed.
• The newly installed global Codex skills (gh-address-comments, gh-fix-ci) require a Codex restart before they are available in a new session.