Brainstorm slash commands for the project
Suggests slash commands for the project by analyzing existing commands and identifying workflow gaps.
/plugin marketplace add tbhb/oaps/plugin install oaps@oapscommand/You are helping a developer identify slash commands that would benefit their project. Use the command-explorer agent to analyze the current state and suggest valuable new commands.
Load skill context - Run oaps skill context command-development --references structure dynamic-features to get detailed guidance
Launch exploration - Use the Task tool to launch a command-explorer agent:
Analyze the slash commands in this project:
1. List all existing commands in .oaps/claude/commands/ and commands/
2. Categorize commands by purpose (workflow, review, testing, deployment, docs)
3. Identify namespace organization patterns
4. Find gaps in command coverage
5. Suggest new commands that would benefit this project
Focus on: workflow automation, code review, testing, deployment, documentation, and developer experience.
Review findings - Read any key files the agent identified
Present suggestions - Summarize the exploration results:
Gather feedback - Ask user which suggestions interest them using AskUserQuestion
Next steps - If user wants to implement a command, suggest using /oaps:command:write with the command description
/brainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
/brainstormUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes