fission-ai__openspec/openspec/changes/add-github-copilot-prompts/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 8822557bcd feat: add GitHub Copilot slash command support

Add GitHub Copilot as a natively supported AI tool with custom slash
commands for OpenSpec workflow operations. This enables teams using
GitHub Copilot to access /openspec-proposal, /openspec-apply, and
/openspec-archive directly from Copilot's chat interface.

Implementation:
- Create GitHubCopilotSlashCommandConfigurator that writes prompts to
  .github/prompts/ directory with YAML frontmatter and $ARGUMENTS
  placeholder following GitHub Copilot's prompt format
- Register GitHub Copilot in AI_TOOLS configuration and slash
  command registry for automatic init/update integration
- Add comprehensive test coverage for prompt generation, updates,
  and extend mode detection
- Update documentation (README and CHANGELOG) to include GitHub
  Copilot in the slash-command support table

The implementation follows the existing SlashCommandConfigurator
pattern and integrates seamlessly with openspec init and openspec
update commands.

2025-10-09 02:15:14 +11:00

1.6 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 GitHub Copilot

WHEN .github/prompts/ contains openspec-proposal.prompt.md, openspec-apply.prompt.md, and openspec-archive.prompt.md
THEN refresh each file using shared templates while preserving the YAML frontmatter
AND update only the OpenSpec-managed block between markers
AND ensure templates include instructions for the relevant workflow stage

Scenario: Missing slash command file

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

1.6 KiB Raw Permalink Blame History