constraint_derivation_index

Routes design and implementation artifacts to bidirectional constraint-derivation Skills and sequences the commonality pass.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill constraint-derivation-index-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: constraint_derivation_index
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/packs/constraint-derivation/constraint_derivation_index
Command: npx skills add https://github.com/synthaicode/XRefKit --skill constraint-derivation-index-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When design specs or code artifacts need constraint derivation, it is unclear which derivation Skill should run, in what order, and whether a secondary commonality pass is required. This Skill removes that ambiguity by classifying artifacts and routing them to the correct downward or upward derivation Skills without implicit AI completion. ## Core Features & Use Cases - Artifact Classification and Routing: Classifies inputs (DDL, UI spec, workflow, API contract, auth matrix, integration notes, generated C# code) and routes them to the applicable downward Skills (design, UI, logic, integration, async, auth) or upward Skills (code, cross, integration scenario). - Secondary Pass Sequencing: Decides explicitly whether commonality_derivation must run after all primary derivation outputs are complete. - Traceable Routing Notes: Writes a dated routing note to work/constraint_derivation/ recording the selected Skill set, execution order, and unresolved gaps. - Use Case: Given a partial UI specification plus generated C# code, the Skill routes the spec to ui_constraint_derivation, the code to code_constraint_derivation, and queues commonality_derivation once both primary outputs exist. ## Quick Start Ask the assistant to route these design and code artifacts through constraint derivation and produce a routing note under work/constraint_derivation/.

Frequently Asked Questions about constraint_derivation_index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route design artifacts to constraint derivation Skills?▼

Classify the artifacts by design area, then route them to every applicable downward Skill such as design, UI, logic, integration, async, or auth constraint derivation. The routing result and rationale are written to a dated note under work/constraint_derivation/.

What is the difference between downward and upward constraint derivation?▼

Downward derivation starts from design artifacts like specs and diagrams, while upward derivation starts from implementation artifacts like generated C# code or mixed code-plus-DDL reviews. Mixed-direction requests route to both sets of Skills.

When does the commonality derivation pass run?▼

The commonality_derivation pass runs only after more than one primary Skill has produced outputs. It is queued after all primary derivation lists are complete, never before.

Can derivation output be treated as approved requirements?▼

No. Derivation output surfaces missing confirmations, hidden assumptions, and boundary scenarios, but it is not approved requirements. Unresolved items must stay explicit and cannot be answered from context completion.

Where are constraint derivation routing notes stored?▼

Routing notes are written to work/constraint_derivation/ with a date-prefixed filename by default. A user-specified output path overrides this default location.