scafforge-pivot

Midstream feature pivots require updating canonical truth and routing downstream surfaces to maintain ticket lineage. This Skill classifies the pivot class, generates a stale-surface map, and constructs a ticket-lineage plan to ensure verifiable downstream routing.

A stale-surface map identifies downstream areas affected by a design pivot that require refresh or restart. You need one when midstream workflow adjustments alter canonical truth, ensuring no outdated restart surfaces remain untracked after routing.

To plan and execute a workflow pivot, invoke the plan_pivot script with the repository root and chosen pivot class. This orchestrates canonical-truth updates, ticket-lineage plan construction, downstream-stage routing, and post-pivot verification.

Yes, this pivot orchestration workflow applies to any repository needing midstream feature changes, design pivots, or workflow adjustments. It handles post-pivot verification and restart surface publication to ensure verifiable handoff regardless of scale.

The best way to verify downstream updates after a midstream workflow adjustment is through a structured post-pivot verification and publication workflow. This confirms canonical truth updates propagated correctly and restart surfaces are published without stale artifacts.

Midstream workflow adjustments fail to propagate when canonical truth is updated without emitting a stale-surface map or routing downstream stages. Without a ticket-lineage plan and post-pivot verification, restart surfaces remain outdated and untracked.