==================================================
JIRA STORY CONTEXT
==================================================

Story ID:
SCRUM-1

Summary:
Employee CRUD

Status:
To Do

Priority:
None

Issue Type:
Task

Assignee:
Unassigned

Reporter:
Sharad Bharsakal

Labels:
None

Components:
None

Parent Epic:
None

Linked Issues:
None

--------------------------------------------------
DESCRIPTION
--------------------------------------------------

Add new crud operation api for an employee

--------------------------------------------------
ACCEPTANCE CRITERIA
--------------------------------------------------

No acceptance criteria found.

--------------------------------------------------
COMMENTS
--------------------------------------------------

No comments.

--------------------------------------------------
AI IMPLEMENTATION INSTRUCTIONS
--------------------------------------------------

You are implementing Jira story SCRUM-1: "Employee CRUD".

SOURCE OF TRUTH
- This context file is the authoritative source for requirements for SCRUM-1.
- Prefer this file over assumptions, memory, or unrelated tickets.
- If this file conflicts with code comments or outdated docs, follow this story and ask before large refactors.

NO HALLUCINATION / NO ASSUMPTIONS
- Do not invent requirements, APIs, UI copy, data fields, or edge cases not supported by this story.
- Do not assume undocumented business rules.
- If something is ambiguous or missing, ask for clarification before implementing.

IMPLEMENTATION GUIDELINES
- Reuse existing code, patterns, utilities, and types in the repository.
- Maintain the current architecture and project conventions.
- Do not introduce new libraries or frameworks unless they are clearly required and justified.
- Deliver production-quality code: clear naming, focused functions, typed interfaces, and maintainability.
- Apply SOLID principles where they improve clarity; avoid over-engineering.
- Handle edge cases, validation, error paths, and empty/null inputs thoughtfully.
- Do not break existing functionality. Prefer additive, backwards-compatible changes.
- Keep changes scoped to this story; avoid drive-by refactors unrelated to the acceptance criteria.

VERIFICATION
- Map your work to the Acceptance Criteria section before considering the task done.
- Call out any criteria that cannot be met with the current information.
- Suggest tests for critical paths introduced or changed by this story.

OUTPUT EXPECTATIONS
- Explain trade-offs briefly when multiple valid approaches exist.
- When unsure, stop and ask rather than guessing.

--------------------------------------------------
IMPLEMENTATION CHECKLIST
--------------------------------------------------

[ ] Requirements understood from Summary, Description, and Acceptance Criteria
[ ] Clarifying questions asked for any ambiguity (no assumptions made)
[ ] Existing code and architecture reviewed for reuse opportunities
[ ] Implementation plan aligned with current project patterns
[ ] Code changes implemented with production quality and clear typing
[ ] Edge cases, validation, and error handling covered
[ ] Existing functionality verified not broken
[ ] Acceptance criteria checked off one by one
[ ] Tests added or updated where appropriate
[ ] No unnecessary new dependencies introduced
[ ] Ready for code review

--------------------------------------------------
END OF CONTEXT
--------------------------------------------------
