fission-ai__openspec/openspec/changes/archive/2026-01-09-fix-codebuddy-frontmatter-fields/specs/cli-init/spec.md at main

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

Files

T

Neroyang 3f67debf65 feat: change the frontmatter of the Codebuddy Slash Commands (#462 )

* feat: change the frontmatter of the Codebuddy Slash Commands

* fix: fix the issue mentioned by coderabbitai

* feat: change the init.test

* feat: change the init.test

---------

Co-authored-by: neroyang <neroyang@tencent.com>

2026-01-09 10:08:59 -08:00

5.8 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 Antigravity

WHEN the user selects Antigravity during initialization
THEN create .agent/workflows/openspec-proposal.md, .agent/workflows/openspec-apply.md, and .agent/workflows/openspec-archive.md
AND ensure each file begins with YAML frontmatter that contains only a description: <stage summary> field followed by the shared OpenSpec workflow instructions wrapped in managed markers
AND populate the workflow body with the same proposal/apply/archive guidance used for other tools so Antigravity behaves like Windsurf while pointing to the .agent/workflows/ directory

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 CodeBuddy Code

WHEN the user selects CodeBuddy Code during initialization
THEN create .codebuddy/commands/openspec/proposal.md, .codebuddy/commands/openspec/apply.md, and .codebuddy/commands/openspec/archive.md
AND populate each file from shared templates that include CodeBuddy-compatible YAML frontmatter for the description and argument-hint fields
AND use square bracket format for argument-hint parameters (e.g., [change-id])
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Cline

WHEN the user selects Cline during initialization
THEN create .clinerules/workflows/openspec-proposal.md, .clinerules/workflows/openspec-apply.md, and .clinerules/workflows/openspec-archive.md
AND populate each file from shared templates so command text matches other tools
AND include Cline-specific Markdown heading frontmatter
AND each template includes instructions for the relevant OpenSpec workflow stage

Scenario: Generating slash commands for Crush

WHEN the user selects Crush during initialization
THEN create .crush/commands/openspec/proposal.md, .crush/commands/openspec/apply.md, and .crush/commands/openspec/archive.md
AND populate each file from shared templates so command text matches other tools
AND include Crush-specific frontmatter with OpenSpec category and tags
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 Factory Droid

WHEN the user selects Factory Droid during initialization
THEN create .factory/commands/openspec-proposal.md, .factory/commands/openspec-apply.md, and .factory/commands/openspec-archive.md
AND populate each file from shared templates that include Factory-compatible YAML frontmatter for the description and argument-hint fields
AND include the $ARGUMENTS placeholder in the template body so droid receives any user-supplied input
AND wrap the generated content in OpenSpec managed markers so openspec update can safely refresh the commands

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

5.8 KiB Raw Permalink Blame History