insurance-feature-delivery

The full skill.

Original instructions from the publisher’s SKILL.md

# Insurance Feature Delivery

## Purpose
Use this skill to convert insurance product requirements into concrete backend and frontend changes with traceable acceptance checks.

## When To Use
- Add or update claim, policy, payment, notification, or support user flows.
- Implement business constraints that span multiple services.
- Build requirement-driven delivery with verification steps.

## Inputs
- Product requirement text.
- Target services and UI surfaces.
- Any event names, DTO fields, and API contracts already in use.

## Project Defaults
- Scope: workspace-shared skill in `.github/skills`.
- Payment success email delivery: secure download links by default.
- Active policy eligibility for claims: `Status = Active` and `EndDate >= today`.
- Days remaining after expiration: show `0` and mark as expired.
- Coverage transparency downloadable summary: PDF only.

## Workflow
1. Normalize requirements into acceptance criteria.
2. Map each criterion to system components.
3. Design event and API contract changes first.
4. Implement backend behavior service-by-service.
5. Implement frontend behavior and validation.
6. Add tests for happy path and failure path.
7. Run verification checklist and produce a change summary.

## Component Mapping For This Project
- Notification and email orchestration: `InsuranceSystem.NotificationService`, plus event producers in Payment, Policy, Ticket, and Claim-related flows.
- Payment outcomes and receipt/document links: `InsuranceSystem.PaymentService` and Notification consumers.
- Policy retrieval and validity data: `InsuranceSystem.PolicyService` and frontend dashboard pages.
- Claim policy eligibility dropdown: claim entry flow in frontend and claim endpoint filter logic.
- Identity/user profile coverage transparency: `InsuranceSystem.IdentityService` profile APIs plus frontend profile page.
- Vehicle form validation before quote: frontend quote flow and backend request validation.

## Decision Points
- Notification trigger style:
  - Use event-driven consumers if an event already exists.
  - Add new integration event if status transition has no event.
- Policy eligibility source:
  - Filter by policy status at API layer if client currently gets all policies.
  - Reuse existing filtered endpoint if it already returns active policies only.
- Document delivery:
  - Return secure URL if documents are stored externally.
  - Stream binary/PDF endpoint if documents are managed locally.
- Days remaining calculation:
  - Compute on backend for consistency and timezone safety.
  - Render countdown on frontend from backend-calculated integer.
- Vehicle validation:
  - Enforce mandatory fields in frontend form UX.
  - Re-validate same fields in backend DTO/model validation.

## Requirement Playbook

### 1) Automated Notification Service
- Trigger emails for:
  - Payment success: include secure links to receipt PDF and policy/insurance documentation.
  - Payment failure: include retry call-to-action.
  - Claim follow-ups: status update emails.
  - Customer support interactions: ticket created/updated/resolved emails.
- Ensure idempotency so duplicate events do not send duplicate emails.
- Persist notification status for retry and audit.

### 2) Dynamic Policy Selection For Claims
- Add API/query to return policies for current user where `Status = Active` and `EndDate >= today`.
- Bind claim form dropdown to active policy IDs only.
- Block submission if selected policy is inactive/expired at submit time.

### 3) Policy Retrieval And Validity Tracking
- Provide dashboard endpoint/UI to:
  - View policy document in browser.
  - Download policy PDF.
  - Display expiration date and days remaining.
- Handle expired policies with explicit visual state.
- Clamp days remaining to `0` after expiration.

### 4) Coverage Transparency And Terms
- On purchase completion, store and expose:
  - Plan/team details.
  - Activation start date.
  - Termination end date.
- Show details in profile and include same data in downloadable PDF summary.

### 5) Mandatory Vehicle Data Validation
- Require VIN, make/model, manufacture year, and registration details before quote generation.
- Add both client-side and server-side validation with clear error messages.
- Prevent quote API call if required data is incomplete.

## Quality Gates
- Functional:
  - All five requirement flows demonstrably work end-to-end.
  - Invalid states are rejected with clear errors.
- Reliability:
  - Notification sending handles retries and duplicate event protection.
- Security and data safety:
  - Document access is authorized per user.
  - No sensitive data leakage in emails or logs.
- UX:
  - User sees actionable messages for failures and required fields.
- Test coverage:
  - Unit tests for validation and days-remaining logic.
  - Integration tests for key API filters and event consumers.
  - Smoke test for payment success/failure notification paths.

## Completion Checklist
- Acceptance criteria mapped to code changes.
- DTO/API/event contracts updated consistently.
- Database migrations added where needed.
- Frontend forms and dashboards updated.
- Tests added and passing for changed behavior.
- Manual verification notes captured for each requirement.

## Output Format
Return:
1. Implemented files by requirement.
2. Contract changes (events, DTOs, API payloads).
3. Test evidence and verification results.
4. Follow-up risks and deferred items.