Use this skill when THB-BBL changes cross UI/API/data boundaries and require coordinated sequencing.
When to use
- Work spans
src/app/**,src/components/**,src/app/api/**/route.ts, andsrc/server/services/**in one change stream. - API contract, schema (
prisma/schema.prisma), serialization, or pipeline semantics can change. - Backend and UI must be updated together to prevent drift.
- Legacy Python parity in
backend/**may need verification or follow-up.
When not to use
- Docs-only tasks.
- UI-only tasks with no backend contract risk.
- Backend-only low-risk tasks with no downstream impact.
- Trivial read-only requests.
Preflight
- Read touched repo guidance (
agents.mdand relevant docs). - Confirm impacted contracts and consumer surfaces inside THB-BBL.
- Identify any TS/Python duplicated logic requiring parity checks.
- Establish rollout order and rollback boundaries.
Stop condition: if contract surface is unclear, stop and resolve before coding.
Execution checklist
- Build an impact matrix: schema/contracts, API/services, UI consumption, and parity dependencies.
- Execute in THB-BBL order: schema/contracts first, API/service implementation second, UI consumption third, end-to-end verification last.
- Coordinate backend semantics and compatibility explicitly.
- Coordinate frontend UX and state handling explicitly.
- Run validations:
npm run lint,npm run typecheck,npm run test, andpython3 -m pytest backend/testswhenbackend/**changes. - Record deferred parity or migration follow-ups with owners.
Fallbacks
- If work resolves backend-only, route primary ownership to
bbl-senior-backend. - If work resolves UI-only, route primary ownership to
bbl-senior-frontend. - If partial rollout is requested, record deferred updates and explicit risk.
Completion contract
Return:
scope_statementimpacted_layerscontract_surfacesschema_impactparity_dependenciesfiles_changedvalidations_runblocked_checksresidual_risksrollback_noteshandoff_dependencies