codex-implementation-plan.md

Obsidian CLI Skills for Codex - Implementation Plan

Date: 2026-04-13 Status: Ready to execute

Phase 1: Foundation

1. Create the repo layout for Codex skills, docs, scripts, and tests.
2. Add maintainer docs:
   • design spec
   • implementation plan
   • command coverage
3. Add .gitignore.

Phase 2: Skill Scaffolding

Create these skill folders:

• skills/obsidian-vault
• skills/obsidian-notes
• skills/obsidian-search
• skills/obsidian-daily
• skills/obsidian-tasks
• skills/obsidian-tags
• skills/obsidian-bookmarks
• skills/obsidian-templates
• skills/obsidian-plugins
• skills/obsidian-ui

For each skill:

1. Write SKILL.md with:
   • trigger description in frontmatter
   • Codex-specific output rules
   • vault targeting guidance
   • domain command reference
   • domain-specific failure guidance
2. Write agents/openai.yaml with:
   • display_name
   • short_description
   • default_prompt

Phase 3: Coverage and Scope Control

1. Document which current CLI commands map into v1 skills.
2. Document intentionally deferred commands.
3. Keep v1 claims aligned with actual coverage.

Phase 4: Validation and Testing

1. Add scripts/validate-skills.sh to run the Codex validator on every skill.
2. Add tests/smoke-test.sh with:
   • CLI presence check
   • command transport preflight
   • optional vault argument
   • safe command execution without eval
3. Add tests/README.md manual validation steps.

Phase 5: Review

Review every skill for:

• frontmatter correctness
• accurate trigger descriptions
• command coverage within domain
• consistency of vault resolution rules
• no Claude-specific packaging or instructions
• no claim of raw-output passthrough that Codex cannot honor

Phase 6: Runtime Verification

1. Run the skill validator.
2. Run smoke tests in an environment where the Obsidian desktop app and CLI transport work.
3. Record any environment-specific failures, especially WSL or redirector issues.