fission-ai__openspec/openspec/changes/add-codex-slash-command-support/specs/cli-update/spec.md at add-github-copilot-cli-support

mirror of https://github.com/Fission-AI/OpenSpec.git synced 2026-09-14 20:16:53 +08:00

Files

T

Tabish Bidiwale 9ae6141eb1 feat: Add codex custom slash command support (#120 )

* Document current cli specs and archive safety

* feat: add Codex slash command support

Add support for generating and updating Codex prompts in `.codex/prompts/` directory:
- Implement CodexSlashCommandConfigurator for managing openspec-*.md prompts
- Update AI_TOOLS configuration to include Codex as an available option
- Add Codex registration in SlashCommandRegistry
- Update documentation to reflect Codex support
- Add comprehensive test coverage for Codex init and update workflows

* feat: complete Codex slash command support implementation

Add comprehensive Codex slash command support with Claude.md integration,
config-driven command management, and full test coverage. Update documentation
and changelog to reflect changes.

* chore: mark all Codex slash command tasks as completed

All tasks for the Codex slash command support feature have been implemented and tested.

* docs: remove Codex-specific note from README

Remove the Codex-specific installation note as it's no longer needed in the main setup instructions. This information is better suited for tool-specific documentation.

2025-10-09 01:55:47 +11:00

2.4 KiB

Raw Permalink Blame History

MODIFIED Requirements

Requirement: Slash Command Updates

The update command SHALL refresh existing slash command files for configured tools without creating new ones.

Scenario: Updating slash commands for Claude Code

WHEN .claude/commands/openspec/ contains proposal.md, apply.md, and archive.md
THEN refresh each file using shared templates
AND ensure templates include instructions for the relevant workflow stage

Scenario: Updating slash commands for Cursor

WHEN .cursor/commands/ contains openspec-proposal.md, openspec-apply.md, and openspec-archive.md
THEN refresh each file using shared templates
AND ensure templates include instructions for the relevant workflow stage

Scenario: Updating slash commands for OpenCode

WHEN .opencode/command/ contains openspec-proposal.md, openspec-apply.md, and openspec-archive.md
THEN refresh each file using shared templates
AND ensure templates include instructions for the relevant workflow stage

Scenario: Updating slash commands for Windsurf

WHEN .windsurf/workflows/ contains openspec-proposal.md, openspec-apply.md, and openspec-archive.md
THEN refresh each file using shared templates wrapped in OpenSpec markers
AND ensure templates include instructions for the relevant workflow stage
AND skip creating missing files (the update command only refreshes what already exists)

Scenario: Updating slash commands for Kilo Code

WHEN .kilocode/workflows/ contains openspec-proposal.md, openspec-apply.md, and openspec-archive.md
THEN refresh each file using shared templates wrapped in OpenSpec markers
AND ensure templates include instructions for the relevant workflow stage
AND skip creating missing files (the update command only refreshes what already exists)

Scenario: Updating slash commands for Codex

GIVEN the global Codex prompt directory contains openspec-proposal.md, openspec-apply.md, and openspec-archive.md
WHEN a user runs openspec update
THEN refresh each file using the shared slash-command templates (including placeholder guidance)
AND preserve any unmanaged content outside the OpenSpec marker block
AND skip creation when a Codex prompt file is missing

Scenario: Missing slash command file

WHEN a tool lacks a slash command file
THEN do not create a new file during update

2.4 KiB Raw Permalink Blame History