fission-ai__openspec/openspec/changes/archive/2025-10-14-add-github-copilot-prompts/specs/cli-init/spec.md at add-coderabbit

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

Files

T

Tabish Bidiwale 345f9dbb45 chore: archive 7 completed changes and update specs (#170 )

Archive completed changes:
- add-non-interactive-init-options
- slim-root-agents-file
- update-cli-init-enter-selection
- add-windsurf-workflows
- add-kilocode-workflows
- add-codex-slash-command-support
- add-github-copilot-prompts

Updates to specs:
- cli-init: Added 7 slash command scenarios (Claude Code, Cursor, OpenCode, Windsurf, Kilo Code, Codex, GitHub Copilot)
- cli-update: Added corresponding update scenarios for all 7 tools
- Fixed MODIFIED requirement deltas to include all existing scenarios before archiving
- Manual correction applied to preserve Windsurf scenario after archive conflicts

All changes validated with --strict flag.

2025-10-14 15:24:49 +11:00

3.6 KiB

Raw Permalink Blame History

MODIFIED Requirements

Requirement: Slash Command Configuration

The init command SHALL generate slash command files for supported editors using shared templates.

Scenario: Generating slash commands for Claude Code

WHEN the user selects Claude Code during initialization
THEN create .claude/commands/openspec/proposal.md, .claude/commands/openspec/apply.md, and .claude/commands/openspec/archive.md
AND populate each file from shared templates so command text matches other tools
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Cursor

WHEN the user selects Cursor during initialization
THEN create .cursor/commands/openspec-proposal.md, .cursor/commands/openspec-apply.md, and .cursor/commands/openspec-archive.md
AND populate each file from shared templates so command text matches other tools
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for OpenCode

WHEN the user selects OpenCode during initialization
THEN create .opencode/commands/openspec-proposal.md, .opencode/commands/openspec-apply.md, and .opencode/commands/openspec-archive.md
AND populate each file from shared templates so command text matches other tools
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Windsurf

WHEN the user selects Windsurf during initialization
THEN create .windsurf/workflows/openspec-proposal.md, .windsurf/workflows/openspec-apply.md, and .windsurf/workflows/openspec-archive.md
AND populate each file from shared templates (wrapped in OpenSpec markers) so workflow text matches other tools
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Kilo Code

WHEN the user selects Kilo Code during initialization
THEN create .kilocode/workflows/openspec-proposal.md, .kilocode/workflows/openspec-apply.md, and .kilocode/workflows/openspec-archive.md
AND populate each file from shared templates (wrapped in OpenSpec markers) so workflow text matches other tools
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Codex

WHEN the user selects Codex during initialization
THEN create global prompt files at ~/.codex/prompts/openspec-proposal.md, ~/.codex/prompts/openspec-apply.md, and ~/.codex/prompts/openspec-archive.md (or under $CODEX_HOME/prompts if set)
AND populate each file from shared templates that map the first numbered placeholder ($1) to the primary user input (e.g., change identifier or question text)
AND wrap the generated content in OpenSpec markers so openspec update can refresh the prompts without touching surrounding custom notes

Scenario: Generating slash commands for GitHub Copilot

WHEN the user selects GitHub Copilot during initialization
THEN create .github/prompts/openspec-proposal.prompt.md, .github/prompts/openspec-apply.prompt.md, and .github/prompts/openspec-archive.prompt.md
AND populate each file with YAML frontmatter containing a description field that summarizes the workflow stage
AND include $ARGUMENTS placeholder to capture user input
AND wrap the shared template body with OpenSpec markers so openspec update can refresh the content
AND each template includes instructions for the relevant OpenSpec workflow stage

3.6 KiB Raw Permalink Blame History