name: feature-delivery description: End-to-end workflow for shipping PetSwipe features cleanly across frontend, backend, docs, and validation.
Use this skill when the user wants a feature implemented, expanded, or refactored across one or more parts of the app.
Workflow
- Inspect the affected area before proposing structure.
- Decide whether the task is frontend-only, backend-only, infra-only, docs-only, or cross-cutting.
- Keep the change coherent across code, navigation, data flow, and docs.
- Validate with the smallest reliable command set for the touched area.
- Update docs when the task changes user-visible behavior, APIs, or deployment posture.
Delegation
If the task is broad, delegate focused analysis to the matching subagent:
frontend-ux-specialistbackend-api-specialistinfra-deployment-auditordocs-curatorpetswipe-reviewer
PetSwipe Rules
- Frontend work should preserve the existing Pages Router structure.
- Backend work should keep routes, controllers, services, entities, and docs aligned.
- Infra work should be validated with render and preflight commands, not claimed complete on inspection alone.
- Doc updates should be made in the same task when behavior changes.
@references/repo-map.md @references/validation.md