메뉴
Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.
Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.
Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.
Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.
Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.
Classify PRs and produce a priority-ordered merge plan. Use when the user says "merge order", "which PR first", "merge plan", or has multiple PRs targeting the same branch that need sequencing.
| name | brainstorming |
| description | Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding. |
Use this skill when the user has a rough idea, wants to explore a feature, or says "let's brainstorm" or "help me design." The goal is to refine an idea into a validated design doc before any code is written.
Transform vague ideas into fully-formed designs through collaborative dialogue. This skill ensures alignment on what to build before committing to how to build it.
01-codebase-research)Bounded context check.
Announce what you will read before reading anything. Follow the 01-codebase-research rule. Read only README.md, CLAUDE.md, and one relevant directory listing.
Clarify with one question at a time. Ask questions to understand purpose, constraints, success criteria, and affected components. Only one question per message. Prefer multiple-choice when the answer space is finite. Stop asking when you have enough context to propose approaches.
Propose 2-3 approaches with trade-offs. Present each approach with a name, pros, cons, and a clear recommendation with a one-sentence rationale. Apply YAGNI — remove features not needed for the stated goal.
Present design in 200-300 word sections. After an approach is chosen, present the design incrementally. After each section, ask "Does this look right so far?" and wait for confirmation. Cover: architecture, components, data flow, error handling, testing strategy.
Write the design file.
Save the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md using today's date and a kebab-case topic slug.
Hand off with artifact path.
Output the exact handoff line referencing the saved file path:
**Next step**: In Cursor Composer, invoke rule 11-writing-plans and provide the path docs/plans/YYYY-MM-DD-<topic>-design.md as context.
A Markdown design document saved to docs/plans/ containing:
docs/plans/YYYY-MM-DD-<topic>-design.md