feat: add /opsx:explore command for exploratory thinking #467
Conversation
Wire up the explore skill and slash command templates to the artifact-experimental-setup command. This adds /opsx:explore as a thinking partner mode for exploring ideas, investigating problems, and clarifying requirements before committing to a change. Changes: - Add imports for getExploreSkillTemplate and getOpsxExploreCommandTemplate - Add explore skill to skills array (generates openspec-explore/SKILL.md) - Add explore command to commands array (generates opsx/explore.md) - Add /opsx:explore to CLI usage message - Update docs/experimental-workflow.md with explore command
📝 WalkthroughWalkthroughThis pull request introduces a new Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Review CompleteYour review story is ready! Comment !reviewfast on this PR to re-generate the story. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @docs/experimental-workflow.md:
- Around line 95-99: The fenced code block showing the command "/opsx:explore"
is missing a language identifier; update that block to include a language like
bash (i.e., change the opening ``` to ```bash) so the static analysis and
consistency with other examples (e.g., the `/opsx:explore` example) are
satisfied.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
docs/experimental-workflow.mdsrc/commands/artifact-workflow.tssrc/core/templates/skill-templates.ts
🧰 Additional context used
🧠 Learnings (7)
📚 Learning: 2025-11-25T01:08:19.004Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: openspec/AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:19.004Z
Learning: Applies to openspec/changes/*/tasks.md : Ensure `tasks.md` contains implementation checklist with numbered sections and checkbox items
Applied to files:
docs/experimental-workflow.mdsrc/commands/artifact-workflow.ts
📚 Learning: 2025-11-25T01:08:02.839Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:02.839Z
Learning: Use `@/openspec/AGENTS.md` to learn how to create and apply change proposals, spec format and conventions, and project structure and guidelines
Applied to files:
docs/experimental-workflow.mdsrc/core/templates/skill-templates.ts
📚 Learning: 2025-11-25T01:08:19.004Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: openspec/AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:19.004Z
Learning: Applies to openspec/changes/**/*.md : Scaffold proposal using `proposal.md`, `tasks.md`, optional `design.md`, and delta specs under `openspec/changes/<id>/`
Applied to files:
docs/experimental-workflow.mdsrc/core/templates/skill-templates.ts
📚 Learning: 2025-11-25T01:08:02.839Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:02.839Z
Learning: Always open `@/openspec/AGENTS.md` when the request mentions planning or proposals (words like proposal, spec, change, plan), introduces new capabilities, breaking changes, architecture shifts, or performance/security work, or sounds ambiguous and needs the authoritative spec before coding
Applied to files:
src/core/templates/skill-templates.ts
📚 Learning: 2025-11-25T01:08:19.004Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: openspec/AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:19.004Z
Learning: Check `openspec/project.md` for project conventions before creating specs
Applied to files:
src/core/templates/skill-templates.ts
📚 Learning: 2025-11-25T01:08:19.004Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: openspec/AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:19.004Z
Learning: Use `openspec archive <change-id> --skip-specs --yes` for tooling-only changes
Applied to files:
src/core/templates/skill-templates.ts
📚 Learning: 2025-11-25T01:08:19.004Z
Learnt from: CR
Repo: Fission-AI/OpenSpec PR: 0
File: openspec/AGENTS.md:0-0
Timestamp: 2025-11-25T01:08:19.004Z
Learning: Run `openspec validate [change-id] --strict` before requesting approval
Applied to files:
src/core/templates/skill-templates.ts
🧬 Code graph analysis (1)
src/commands/artifact-workflow.ts (1)
src/core/templates/skill-templates.ts (2)
getExploreSkillTemplate(21-301)getOpsxExploreCommandTemplate(899-1069)
🪛 markdownlint-cli2 (0.18.1)
docs/experimental-workflow.md
96-96: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🔇 Additional comments (12)
docs/experimental-workflow.md (2)
85-85: LGTM!The new
/opsx:explorecommand is correctly added to the Commands table with an accurate description that aligns with the template content.
530-530: LGTM!Good addition to the Tips section - recommending
/opsx:explorebefore committing to a change aligns well with the exploratory thinking use case.src/commands/artifact-workflow.ts (5)
31-31: LGTM!The import statement correctly adds the two new template functions (
getExploreSkillTemplate,getOpsxExploreCommandTemplate) alongside the existing template imports.
796-796: LGTM!Template instantiation follows the established pattern for other skills and commands.
Also applies to: 805-805
814-822: LGTM!The explore skill is correctly added to the skills array with the appropriate directory name
openspec-explore, following the naming convention of other skills.
845-853: LGTM!The explore command is correctly added to the commands array with the filename
explore.md, consistent with other command entries.
905-905: LGTM!The console output correctly lists
/opsx:explorefirst in the slash commands section, with an accurate description that matches the command's purpose.src/core/templates/skill-templates.ts (5)
17-25: LGTM!The function signature and return type follow the established
SkillTemplateinterface pattern. The description clearly conveys the exploratory thinking-partner purpose.
25-301: Well-structured explore skill template.The template provides comprehensive guidance for the AI agent including:
- Clear stance definition (curious, visual, adaptive, patient, grounded)
- Concrete examples with ASCII diagrams for different entry points
- OpenSpec integration awareness with
openspec list --jsonusage- Appropriate guardrails preventing auto-capture behavior
The extensive examples for different user entry points (vague idea, specific problem, mid-implementation, comparison) are particularly helpful for guiding agent behavior.
895-905: LGTM!The command template follows the established
CommandTemplateinterface with appropriate metadata (name, description, category, tags).
905-1069: Content largely duplicates skill template - acceptable pattern.The command template content mirrors the skill template with the addition of input handling guidance (lines 909-914). This duplication is consistent with how other skill/command pairs in this file are structured (e.g.,
getNewChangeSkillTemplatevsgetOpsxNewCommandTemplate).The command template appropriately adds the
**Input**section explaining the argument handling, which the skill template omits since skills are triggered by natural language rather than explicit slash commands.
324-374: Minor wording update in existing template - consistent improvement.The changes from "Selected schema/workflow" to "Schema/workflow being used" and related phrasing updates are consistent style improvements across the templates. These are minor documentation clarifications.
| ### Explore an idea | ||
| ``` | ||
| /opsx:explore | ||
| ``` | ||
| Think through ideas, investigate problems, compare options. No structure required - just a thinking partner. When insights crystallize, transition to `/opsx:new` or `/opsx:ff`. |
There was a problem hiding this comment.
Add a language identifier to the fenced code block.
The static analysis tool flagged the missing language specifier on the fenced code block. For consistency with other usage examples in this file (e.g., line 103), add bash or leave it as a generic text block with an explicit identifier.
Proposed fix
### Explore an idea
-```
+```bash
/opsx:explore
</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
### Explore an idea
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
96-96: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In @docs/experimental-workflow.md around lines 95 - 99, The fenced code block
showing the command "/opsx:explore" is missing a language identifier; update
that block to include a language like bash (i.e., change the opening ``` to
```bash) so the static analysis and consistency with other examples (e.g., the
`/opsx:explore` example) are satisfied.
Summary
artifact-experimental-setup/opsx:exploreas a thinking partner mode for exploring ideas, investigating problems, and clarifying requirements before committing to a changeChanges
src/commands/artifact-workflow.ts:getExploreSkillTemplateandgetOpsxExploreCommandTemplateopenspec-explore/SKILL.md)opsx/explore.md)/opsx:exploreto CLI usage messagedocs/experimental-workflow.md:/opsx:exploreto the Commands tableTest plan
npm run build)openspec artifact-experimental-setupgenerates explore skill and command files/opsx:explorein Claude Code🤖 Generated with Claude Code
Summary by CodeRabbit
/opsx:explorecommand, enabling users to explore and validate ideas before committing to changes.✏️ Tip: You can customize this high-level summary in your review settings.