# Agent Guidelines

## Jira Issue Workflow

- If anyone in the company provides a Jira issue key such as `TDH-1234` or a Jira hyperlink, fetch the Jira issue details before planning or implementing the change.
- Read at least the issue summary, description, status, assignee, labels, issue type, and priority. If requirements are still unclear, inspect comments or ask a concise follow-up before coding.
- Use the Jira REST API with credentials from local environment variables or an approved secret store. Do not hard-code or commit Jira API keys, API tokens, passwords, cookies, or personal access tokens.
- Everyone working with Jira issues should configure their own local Jira credentials before starting: set `JIRA_EMAIL` to their company email and `JIRA_API_TOKEN` to their own Jira API token in their shell profile, local env file, or approved secret manager. Do not reuse another person's token.
- Example local shell setup: `export JIRA_EMAIL=you@kommunicate.io` and `export JIRA_API_TOKEN=your-local-token`. If these are unavailable, ask the user to provide access through a secure local mechanism instead of adding secrets to the repository.
- Treat Jira descriptions as the source of requirements. Do not rely only on the ticket title, branch name, or a short user paraphrase when a Jira key or URL is available.
- When work is completed, create a branch and PR that only contains the relevant changes. For small related issues, one PR can be acceptable; for complex or larger issues, prefer separate PRs.
- After filing a PR, add the PR link back to the Jira issue and move/update the issue according to the team's current workflow when requested.