workflow-adapter

Execute all agents using teammate coordination

Interactive brainstorming to refine a feature

Generate implementation plan with agent task assignments

Review feature documents using reviewer agent

Generate specification from brainstorming

Integrated feature workflow (context -> brainstorming -> spec -> plan -> review)

Generate implementation plan for a triaged fix

Review fix documents using reviewer agent

Triage a bug or technical debt issue with root cause analysis

Integrated fix workflow (triage -> plan -> review)

Initialize the workflow-adapter system in the current project.

Validate workflow progress and add tasks if needed

Check team execution status

Validate workflow completion with orchestrator and reviewer

Use this agent when code review or document validation is needed. <example> Context: User wants to review feature documents user: "Review the spec for the login feature" assistant: "I'll use the reviewer agent to validate the feature specification." <commentary> Document review requires specialized validation agent. </commentary> </example> <example> Context: Code review needed user: "Check if the implementation matches the spec" assistant: "I'll use the reviewer agent to verify the implementation against the specification." <commentary> Spec compliance validation is a core reviewer responsibility. </commentary> </example>

This skill should be used when the user asks to "codex에게 물어봐", "codex한테 질문해봐", "codex 의견 들어봐", "codex에게 리뷰해달라고 해", "ask codex", "ask codex about this", "get codex opinion", "check with codex", "consult codex", "what does codex think", "run this by codex", "codex에게 보여줘", or wants to delegate a question, review, or consultation to Cursor's agent CLI (codex model) about code, architecture, or any topic.

This skill should be used when the user asks to "리서치해줘", "조사해줘", "컨텍스트 수집해줘", "context 모아줘", "사전 조사", "배경 조사해줘", "기술 리서치", "아키텍처 리서치", "research this", "gather context", "investigate this topic", "explore this before we start", "do a deep dive into", "help me understand the landscape", "what should I know before building", "explore options for", or wants to gather comprehensive context through parallel expert research combined with interactive user refinement before starting implementation work. Also used when the feature workflow needs an enhanced context-gathering stage.

This skill should be used when the user wants to modify, update, or revise an existing note in their Obsidian vault. Common triggers include "노트 수정해줘", "노트 업데이트해줘", "노트 내용 바꿔줘", "기존 노트에 추가해줘", "노트 편집", "vault 노트 수정", "edit my note", "update the note", "revise my note", "add to my note", "modify the note", "append to note", or any request to change the content of an existing Obsidian vault note.

This skill should be used when the user asks to "노트 정리해줘", "노트로 만들어줘", "obsidian에 저장해줘", "obsidian에 정리", "vault에 저장", "논의 내용 정리해줘", "대화 내용 정리", "지금까지 내용 정리", "마크다운으로 정리", "obsidian 노트 작성", "save to obsidian", "write notes", "create a note", "summarize this conversation", "organize into a note", "save my notes", "export to obsidian", or wants to capture, organize, and persist the current AI conversation as a structured Obsidian-compatible markdown note with frontmatter, wikilinks, and tags.

This skill should be used when the user wants to search their Obsidian vault for notes, references, or previously recorded information to use as context in the current conversation. Common triggers include "노트에서 찾아줘", "노트 검색해줘", "vault에서 찾아봐", "이전에 정리한 거 찾아줘", "관련 노트 찾아줘", "obsidian에서 검색", "내 노트에서", "search my notes", "find in vault", "look up in obsidian", "find notes about", "what did I write about", or any request to retrieve information from an Obsidian vault.