|
| 1 | +## MODIFIED Requirements |
| 2 | +### Requirement: AI Tool Configuration Details |
| 3 | + |
| 4 | +The command SHALL properly configure selected AI tools with OpenSpec-specific instructions using a marker system. |
| 5 | + |
| 6 | +#### Scenario: Configuring Claude Code |
| 7 | + |
| 8 | +- **WHEN** Claude Code is selected |
| 9 | +- **THEN** create or update `CLAUDE.md` in the project root directory (not inside openspec/) |
| 10 | +- **AND** populate the managed block with a short stub that points teammates to `@/openspec/AGENTS.md` |
| 11 | + |
| 12 | +#### Scenario: Configuring CodeBuddy Code |
| 13 | + |
| 14 | +- **WHEN** CodeBuddy Code is selected |
| 15 | +- **THEN** create or update `CODEBUDDY.md` in the project root directory (not inside openspec/) |
| 16 | +- **AND** populate the managed block with a short stub that points teammates to `@/openspec/AGENTS.md` |
| 17 | + |
| 18 | +#### Scenario: Configuring Cline |
| 19 | + |
| 20 | +- **WHEN** Cline is selected |
| 21 | +- **THEN** create or update `CLINE.md` in the project root directory (not inside openspec/) |
| 22 | +- **AND** populate the managed block with a short stub that points teammates to `@/openspec/AGENTS.md` |
| 23 | + |
| 24 | +#### Scenario: Creating new CLAUDE.md |
| 25 | + |
| 26 | +- **WHEN** CLAUDE.md does not exist |
| 27 | +- **THEN** create new file with stub instructions wrapped in markers so the full workflow stays in `openspec/AGENTS.md`: |
| 28 | +```markdown |
| 29 | +<!-- OPENSPEC:START --> |
| 30 | +# OpenSpec Instructions |
| 31 | + |
| 32 | +This project uses OpenSpec to manage AI assistant workflows. |
| 33 | + |
| 34 | +- Full guidance lives in '@/openspec/AGENTS.md'. |
| 35 | +- Keep this managed block so 'openspec update' can refresh the instructions. |
| 36 | +<!-- OPENSPEC:END --> |
| 37 | +``` |
| 38 | + |
| 39 | +### Requirement: Slash Command Configuration |
| 40 | +The init command SHALL generate slash command files for supported editors using shared templates. |
| 41 | + |
| 42 | +#### Scenario: Generating slash commands for Claude Code |
| 43 | +- **WHEN** the user selects Claude Code during initialization |
| 44 | +- **THEN** create `.claude/commands/openspec/proposal.md`, `.claude/commands/openspec/apply.md`, and `.claude/commands/openspec/archive.md` |
| 45 | +- **AND** populate each file from shared templates so command text matches other tools |
| 46 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 47 | + |
| 48 | +#### Scenario: Generating slash commands for CodeBuddy Code |
| 49 | +- **WHEN** the user selects CodeBuddy Code during initialization |
| 50 | +- **THEN** create `.codebuddy/commands/openspec/proposal.md`, `.codebuddy/commands/openspec/apply.md`, and `.codebuddy/commands/openspec/archive.md` |
| 51 | +- **AND** populate each file from shared templates so command text matches other tools |
| 52 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 53 | + |
| 54 | +#### Scenario: Generating slash commands for Cline |
| 55 | +- **WHEN** the user selects Cline during initialization |
| 56 | +- **THEN** create `.clinerules/openspec-proposal.md`, `.clinerules/openspec-apply.md`, and `.clinerules/openspec-archive.md` |
| 57 | +- **AND** populate each file from shared templates so command text matches other tools |
| 58 | +- **AND** include Cline-specific Markdown heading frontmatter |
| 59 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 60 | + |
| 61 | +#### Scenario: Generating slash commands for Cursor |
| 62 | +- **WHEN** the user selects Cursor during initialization |
| 63 | +- **THEN** create `.cursor/commands/openspec-proposal.md`, `.cursor/commands/openspec-apply.md`, and `.cursor/commands/openspec-archive.md` |
| 64 | +- **AND** populate each file from shared templates so command text matches other tools |
| 65 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 66 | + |
| 67 | +#### Scenario: Generating slash commands for OpenCode |
| 68 | +- **WHEN** the user selects OpenCode during initialization |
| 69 | +- **THEN** create `.opencode/commands/openspec-proposal.md`, `.opencode/commands/openspec-apply.md`, and `.opencode/commands/openspec-archive.md` |
| 70 | +- **AND** populate each file from shared templates so command text matches other tools |
| 71 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 72 | + |
| 73 | +#### Scenario: Generating slash commands for Windsurf |
| 74 | +- **WHEN** the user selects Windsurf during initialization |
| 75 | +- **THEN** create `.windsurf/workflows/openspec-proposal.md`, `.windsurf/workflows/openspec-apply.md`, and `.windsurf/workflows/openspec-archive.md` |
| 76 | +- **AND** populate each file from shared templates (wrapped in OpenSpec markers) so workflow text matches other tools |
| 77 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 78 | + |
| 79 | +#### Scenario: Generating slash commands for Kilo Code |
| 80 | +- **WHEN** the user selects Kilo Code during initialization |
| 81 | +- **THEN** create `.kilocode/workflows/openspec-proposal.md`, `.kilocode/workflows/openspec-apply.md`, and `.kilocode/workflows/openspec-archive.md` |
| 82 | +- **AND** populate each file from shared templates (wrapped in OpenSpec markers) so workflow text matches other tools |
| 83 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
| 84 | + |
| 85 | +#### Scenario: Generating slash commands for Codex |
| 86 | +- **WHEN** the user selects Codex during initialization |
| 87 | +- **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) |
| 88 | +- **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) |
| 89 | +- **AND** wrap the generated content in OpenSpec markers so `openspec update` can refresh the prompts without touching surrounding custom notes |
| 90 | + |
| 91 | +#### Scenario: Generating slash commands for GitHub Copilot |
| 92 | +- **WHEN** the user selects GitHub Copilot during initialization |
| 93 | +- **THEN** create `.github/prompts/openspec-proposal.prompt.md`, `.github/prompts/openspec-apply.prompt.md`, and `.github/prompts/openspec-archive.prompt.md` |
| 94 | +- **AND** populate each file with YAML frontmatter containing a `description` field that summarizes the workflow stage |
| 95 | +- **AND** include `$ARGUMENTS` placeholder to capture user input |
| 96 | +- **AND** wrap the shared template body with OpenSpec markers so `openspec update` can refresh the content |
| 97 | +- **AND** each template includes instructions for the relevant OpenSpec workflow stage |
0 commit comments