원클릭으로
brainstorm
Structured brainstorming for exploring new features or solving complex problems
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Structured brainstorming for exploring new features or solving complex problems
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scope, architect, and plan new tasks
Multi-angle code review before merging
Summarize the day's work and put it in context
Wrap up work — atomic commits and push to origin
Full end-to-end (E2E) testing skill utilizing the browser. Make sure to use this skill whenever the user asks to "test the app", "run end to end tests", "verify the UI", "check if the app works", or wants you to use the browser to interact with and test the application flow. This skill orchestrates creating a test plan, getting user approval, navigating the application using the browser, independently fixing obstacles, and generating a progressive test report.
Analyzes the current project repository and workflows to provide a high-level status report. Use this skill when the user asks for a status update, wants to know "what's next", asks where development left off, or needs a summary of recent work to regain context. Do NOT use this skill if the user is asking you to actually implement the next feature, commit code, or search the codebase for specific files.
| name | brainstorm |
| description | Structured brainstorming for exploring new features or solving complex problems |
Run a structured divergent-to-convergent thinking process before diving into planning or implementation. Useful when exploring a new feature space or tackling a thorny architectural problem.
Define the problem space, constraints, and desired outcomes, then rigorously challenge the premise:
Explore multiple, distinctly different approaches to solving the problem. Do not commit to one yet. Consider:
Laravel, Nuxt) handle this natively?Note: The agent should list the pros/cons, feasibility, and risk for each approach.
Evaluate the explored options against the constraints from Step 1.
Generate a structured brief.
Write the output to docs/brainstorms/YYYY-MM-DD-[topic]-brainstorm.md.
# Brainstorm: [Topic]
**Date:** YYYY-MM-DD
**Status:** Completed
## 1. Framing
- **Goal:** [brief]
- **Constraints:** [brief]
## 2. Exploration
[Summary of the 3-4 distinct approaches considered, with pros/cons]
## 3. Recommendation
**Chosen Approach:** [Name]
**Rationale:** [Why this won out]
**Rejected Alternatives:** [Why the others were dropped]
## 4. Open Questions
- [Any unknowns that need to be resolved during the Planning phase]
docs/brainstorms/. Do not just output text to the chat.origin: reference when subsequently running /lfg (Planning phase).