AgentSkillsCN

manage-env-module-slices

强制执行模块级的环境所有权与需求声明，并依据仓库环境契约，同步模块环境分片（modules/<module_id>/MANIFEST.yaml 中的 env.owns/env.requires）。在新增或变更模块的环境依赖时，或在环境契约更新前后，通过此流程及时发现冲突并刷新模块上下文分片。

SKILL.md
--- frontmatter
name: manage-env-module-slices
description: Enforce module-level env ownership/requirements and sync module env slices (env.owns/env.requires in modules/<module_id>/MANIFEST.yaml) against the repo env contract. Use when adding or changing a module's env dependencies, or before/after env contract updates to detect conflicts and refresh module context slices.

Manage Env Module Slices

Purpose

Enforce module-level env boundaries (owns/requires) without modifying the env contract, and generate per-module env slices for LLM context.

The manage-env-module-slices workflow does not change env/contract.yaml. It only validates and syncs module slices.

Required Inputs

  • •Module manifests: modules/<module_id>/MANIFEST.yaml
  • •Env contract: env/contract.yaml

Outputs

  • •modules/<module_id>/interact/env-slice.json (default output)
  • •Updated module registry: modules/<module_id>/interact/registry.json

Procedure

Phase 0 — Contract readiness (mandatory)

  1. •Confirm env/contract.yaml exists and defines the required variables.
  2. •If the contract is missing, initialize the repo-level env contract SSOT (then resume):
    • •Check docs/project/env-ssot.json is repo-env-contract
    • •If first-time setup, scaffold a minimal safe contract (no secrets): python3 -B -S .ai/skills/features/environment/env-contractctl/scripts/env_contractctl.py init --root . --out .ai/.tmp/env-contract/bootstrap.md
  3. •If new keys are needed, update env/contract.yaml via the env-contractctl workflow (and regenerate artifacts), then resume this skill.

Phase 1 — Declare module boundaries

  1. •In modules/<module_id>/MANIFEST.yaml, add or update:
yaml
env:
  owns:
    - key: SERVICE_API_KEY
  requires:
    - LOG_LEVEL

Rules:

  • •Use exact keys from env/contract.yaml.
  • •Only one module may own a given key.

Phase 2 — Preflight validation (mandatory)

  1. •Run strict validation:
    • •node .ai/scripts/modules/env-contractctl-module.mjs verify
    • •Optional: node .ai/scripts/modules/env-contractctl-module.mjs verify --strict
  2. •Check ownership conflicts:
    • •node .ai/scripts/modules/env-contractctl-module.mjs conflicts
  3. •If any errors or conflicts are reported, STOP and resolve:
    • •Fix missing or invalid keys.
    • •Resolve ownership conflicts (one owner per key).

Phase 3 — Preview slice (recommended)

  1. •Export a preview slice for review:
    • •node .ai/scripts/modules/env-contractctl-module.mjs export-slice --module-id <module_id>
  2. •Ask for confirmation before writing slices, especially if updating multiple modules.

Checkpoint: request explicit approval before writing slices.

code
[APPROVAL REQUIRED]
I am ready to generate and write module slices.

- Command: sync-slices
- Scope: all modules (or a single module if --module-id is used)

Type "approve slices" to proceed.

Phase 4 — Sync module slices (writes)

  1. •Generate slices for all modules (requires explicit approval):
    • •node .ai/scripts/modules/env-contractctl-module.mjs sync-slices
  2. •Or target a single module:
    • •node .ai/scripts/modules/env-contractctl-module.mjs sync-slices --module-id <module_id>
  3. •To avoid registry updates, add --no-registry.

Verification

  • • verify passes with no errors
  • • conflicts reports no ownership collisions
  • • modules/<module_id>/interact/env-slice.json exists and matches declared owns/requires
  • • Module registry updated with env-slice artifact (unless --no-registry)

Boundaries

  • •MUST NOT modify env/contract.yaml in the manage-env-module-slices workflow.
  • •MUST NOT store secrets in repo artifacts.
  • •MUST NOT treat module slices as SSOT.
  • •MUST resolve ownership conflicts before syncing slices.
  • •MUST obtain explicit approval before running sync-slices for all modules.