Menu
Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | legacy-storeops-workbench-schema |
| description | Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders. |
| domain | services |
| confidence | high |
| source | earned |
Use this when the sample needs believable store-manager and dispatch workbench data without pretending the portal and desktop shell are backed by one tidy aggregate. It fits legacy SQL Server estates where operational status, order lookup, and workforce notes grew into side tables around the core dispatch board.
Store) separate from operational snapshot data (StoreOperationsStatus) so manager-on-duty, board mode, and escalation notes can drift independently.StoreOrder table and let DispatchTicket point back to it through a nullable foreign key; delivery and carryout should overlap, not collapse into one fake workflow.data\sqlserver\before\StoreOps\02-schema.sqldata\sqlserver\before\StoreOps\03-seed-data.sqlsrc\before\Fabrikam.EnterprisePizza.Business.StoreOps\Services\StoreOperationsWorkbenchService.cssrc\before\Fabrikam.EnterprisePizza.StoreOps.Portal\Default.aspx.csStore until it becomes a junk drawer for every live operational field.Squad branching model: main-only workflow with feature branches
{what this skill teaches agents}
Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.
Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
Restack a child PR onto main after its base PR merges, then revalidate before clearing draft.