nexus

You can extract reusable skills from a codebase by applying context-driven-development patterns to derive and maintain skills from repository code and project contexts, enabling cross-project reuse and rapid team onboarding.

Context-driven development governance models orchestration and rules for commit-based workflows, enforcing canonical frontmatter, sub-skill references, and documented usage rules across multiple project sub-skills.

Standardize context workflow orchestration by centralizing sub-skill coordination, enforcing canonical frontmatter, and applying documented selection rules to determine which sub-skill applies in a given project context.

Use context-driven-development for workflow governance and skill-from-codebase for deriving skills from repository code, consulting the selection guidance to determine the correct application for your project context.

Yes, context workflow orchestration operates without external dependencies, using canonical frontmatter and sub-skill references to coordinate context-driven-development patterns and codebase skill extraction natively.

Deriving skills from repository code is limited to Nexus-oriented project contexts and requires enforcing canonical frontmatter, sub-skill references, and documented usage rules to maintain cross-project consistency.