Developer Tool Workflows

Orchestrates the three-skill Semantius pipeline (semantius-architect → semantius-analyst → semantius-modeler) and handles administrative operations on a Semantius instance. Trigger when the user's intent spans more than one skill, when they reference a remote blueprint URL, when they say "deploy this blueprint", "deploy these blueprints", "deploy all of these", "set up these systems", "build me a system and deploy it", "set up a CRM end-to-end", "clone the candidate-crm blueprint and deploy", "what's deployed in our instance?", "status of semantius", "audit this file" (without naming a specific skill), "back up the catalog", "snapshot the module", "get started", "I'm new here, set this up", or any variation that requires inspecting workspace artifacts and routing to the right sub-skill. Also trigger when a deploy request carries multiple URLs, paths, or a glob. Do NOT trigger when the user explicitly invokes a single sub-skill ("audit this spec with semantius-analyst", "run the modeler"), let those direct calls go through. The admin skill is the front door for end-to-end and ambiguous requests, not a wrapper around every Semantius interaction.

Reconciles a -semantic-blueprint.md (produced by the semantius-architect skill) against the live Semantius catalog and produces a deployable -semantic-spec.md. Trigger when the user has a blueprint and wants it turned into a deployable spec, or when they say: "reconcile this blueprint with semantius", "what's already in the catalog that this blueprint can reuse", "extend the blueprint into a deployable spec", "fold this blueprint into the live catalog", "make the blueprint match what we already have", or any variation that involves comparing a blueprint to live Semantius state and filling in field-level detail. The analyst is the gatekeeper of the unified catalog: it inspects every blueprint entity against built-ins, same-module duplicates, shared masters, cross-module collisions, and near-name collisions; drives the user through merge / rename / reuse / promote decisions; confirms which optional blueprint entities to include; and only then elicits field-level detail (fields, formats, validation rules, computed fields, input-type rules, select rules) for the entities the spec will OWN. Reused entities are referenced, not respecified. Output: a -semantic-spec.md that the semantius-modeler skill deploys with no further interactive decisions.