foundation-crew

Coordinate ownership of core types and coverage models across Apex crates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sahajamoth/apex --skill foundation-crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundation-crew
Source: https://github.com/sahajamoth/apex/tree/main/.agents/skills/foundation-crew
Command: npx skills add https://github.com/sahajamoth/apex --skill foundation-crew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The foundation crew owns and coordinates core project types, coverage models, and intermediate representations to prevent drift across shared crates.

Core Features & Use Cases

  • Defines ownership boundaries for apex-core, apex-coverage, and apex-mir.
  • Enforces consistent patterns, tests, and downstream impact assessment for partner crews.
  • Guides safe changes and cross-crate coordination with minimal risk.

Quick Start

Review required core changes, implement them in apex-core/apex-coverage/apex-mir following the workflow, and run the tests to validate impact.

Frequently Asked Questions about foundation-crew

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

FAQPage Schema
How do I coordinate core type changes across shared crates without causing drift?

To coordinate core type changes without drift, implement updates in apex-core, apex-coverage, and apex-mir by following the foundation-crew workflow, evaluating downstream impact on partner crews to ensure tests reflect the modifications.

What is the foundation-crew process for shared type ownership and coverage models?

The foundation-crew process defines strict ownership boundaries for apex-core, apex-coverage, and apex-mir, enforcing consistent patterns, tests, and downstream impact assessments to prevent representation drift across shared crates.

How do I validate intermediate representation updates for the Apex codebase?

To validate intermediate representation updates, apply changes to apex-mir following the foundation workflow, then run the test suite to assess downstream impact and validate that partner crews experience no adverse effects.

When do I need to follow the foundation-crew workflow for crate modifications?

You need to follow the foundation-crew workflow when applying changes to shared foundational crates, ensuring that core type definitions, testing guidelines, and downstream coordination requirements are safely satisfied.

What are the limitations of modifying apex-core types directly without coordination?

Modifying apex-core types directly without coordination risks type drift and breaks downstream partner crews, which is why the foundation workflow enforces cross-crate impact assessment and consistent testing patterns.