Pilot loadout for agentd skills after Codex compatibility is available

[pentaxis93]

Problem

agentd currently uses ad hoc project-level skill path wiring (.agents/skills plus a temporary .claude/skills alias) so both Codex and Claude can discover skills. This is intentionally temporary and drift-prone.

Goal

Pilot loadout in agentd as the skills activation/discovery mechanism once loadout supports Codex compatibility.

Blocker (must be resolved first)

• Upstream loadout has released and documented Codex compatibility sufficient for project-level skill discovery in agentd.

Scope (when unblocked)

• Keep existing skill content in-repo.
• Configure loadout for agentd project scope.
• Replace manual aliasing flow with loadout-managed linking for this repo.
• Update docs to describe the new flow.

Out of Scope

• Org-wide migration.
• Personal/global skill migration beyond what is required for this pilot.
• Hardening/CI enforcement beyond basic pilot validation.

Pilot Acceptance Criteria

• Codex and Claude both discover the same project skills in agentd using loadout configuration.
• Existing skill behavior remains unchanged (discovery plumbing only).
• Repository docs describe the pilot setup and rollback path.
• Manual fallback (current alias approach) is documented in case of pilot failure.

Verification Scenarios (when unblocked)

1. Fresh agentd clone + configured loadout exposes project skills to both tools.
2. Skill visible via one tool is visible via the other (same set).
3. Removing/disabling a skill in loadout reflects in both tool discovery paths.
4. Rollback to current manual alias method is straightforward and documented.

Notes

This issue stays blocked until upstream Codex compatibility in loadout is confirmed.

[pentaxis93]

Implemented and merged in PR #15 (commit 0a459fa). Closing as complete.