# Feature Delivery

> End-to-end workflow for shipping PetSwipe features cleanly across frontend, backend, docs, and validation.

- Skill: `hoangsonww/feature-delivery-2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add hoangsonww/feature-delivery-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hoangsonww/feature-delivery-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: hoangsonww (https://skillmd.com/u/hoangsonww)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hoangsonww/feature-delivery-2

---


Use this skill when the user wants a feature implemented, expanded, or refactored across one or more parts of the app.

## Workflow

1. Inspect the affected area before proposing structure.
2. Decide whether the task is frontend-only, backend-only, infra-only, docs-only, or cross-cutting.
3. Keep the change coherent across code, navigation, data flow, and docs.
4. Validate with the smallest reliable command set for the touched area.
5. 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-specialist`
- `backend-api-specialist`
- `infra-deployment-auditor`
- `docs-curator`
- `petswipe-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