AI Feature Checklist

Last updated: April 16, 2026

Use this checklist for any future platform change that affects AI assistant behavior, generated files, skills, agents, MCP connectivity, or project guidance.

1. Scope The Change

[ ] Decide whether the change is shared across assistants or assistant-specific.
[ ] Identify the canonical source of truth.
[ ] Identify every render target that should be updated.
[ ] Document any intentional Claude/Codex differences before implementation.

2. Update The Right Source

[ ] Shared repo guidance changed in AGENTS.md.template if needed.
[ ] Shared skill content changed in cli/templates/project-skills/ if needed.
[ ] Claude agent templates changed in cli/templates/project-agents/ if needed.
[ ] Codex agent templates changed in cli/templates/project-codex-agents/ if needed.
[ ] Assistant config templates changed in the platform template files if needed.

3. Wire The CLI Paths

[ ] wdg create generates the new output where appropriate.
[ ] wdg <project> ai-config sync refreshes the new output where appropriate.
[ ] wdg <project> skills sync deploys the new output where appropriate.
[ ] repo clone or attach flows also receive the new output where appropriate.
[ ] user-facing command text remains assistant-agnostic unless there is a deliberate exception.

4. Verify Discovery Paths

[ ] Claude-facing skill files land in .claude/skills/ if applicable.
[ ] Codex-facing skill files land in .agents/skills/ if applicable.
[ ] Claude agent files land in .claude/agents/ if applicable.
[ ] Codex agent files land in .codex/agents/ if applicable.
[ ] Codex project config lands in .codex/config.toml if applicable.

5. Check MCP And Tooling Parity

[ ] Required MCP servers are present for both assistants when parity is intended.
[ ] Any narrower or broader tool surface is explicitly documented.
[ ] Generated config values use the correct project-scoped ports and URLs.

6. Update Docs

[ ] Update docs in docs/codex-update/ when the maintenance model or migration status changes.
[ ] Update user-facing docs such as README.md, QUICKSTART.md, docs/claude-config.md, or docs/MCP_GUIDE.md when behavior changes.
[ ] Update help text in the CLI when command behavior or scope changes.
[ ] Remove stale Claude-only wording if the feature is now multi-assistant.

7. Add Tests

[ ] Add or update BATS coverage for create-time generation.
[ ] Add or update BATS coverage for sync behavior.
[ ] Add or update tests for both Claude and Codex outputs when both are in scope.
[ ] Cover overwrite versus preserve behavior when sync commands support --force.

8. Run Verification

[ ] Run bash -n on every changed shell script.
[ ] Run the relevant BATS tests when available.
[ ] Run a manual smoke test for generated file contents when BATS is unavailable or insufficient.
[ ] Verify help output if command wording changed.

9. Pre-Merge Questions

[ ] If this feature is shared, would a new project and an existing project both receive it?
[ ] If this feature is Codex-specific, is that difference clearly justified?
[ ] If this feature is Claude-specific, is that difference clearly justified?
[ ] Are generated files still owned by templates and sync commands rather than manual edits?
[ ] Can another engineer see the maintenance path without tribal knowledge?