Sprintify Sync

Every sprintify-derived project forked the base code at some point and has drifted since. The base-code skills (/audits, /authorization, /confirm-request, /jobs-development, /notification-development, /translations) check applicability first and skip themselves when the fork predates the feature they document. This skill closes that gap: it brings the project's copy of one feature area up to the latest sprintify base code, so the corresponding skill fully applies.

Code flows from sprintify into the project, never the other way. Project-only files are never deleted, and project customizations are merged around, not overwritten.

Process

1. Scope the sync

The argument names a base-code skill or feature area (e.g. /sprintify-sync notification-development, /sprintify-sync audits). No argument: ask which area to sync.

Anchor paths per area — starting points, never an exhaustive list: