ravenclaw-context
Load work context from Ravenclaw and prepare for task execution. Use at the start of a new session or when switching between tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Load work context from Ravenclaw and prepare for task execution. Use at the start of a new session or when switching between tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ravenclaw-context |
| description | Load work context from Ravenclaw and prepare for task execution. Use at the start of a new session or when switching between tasks. |
This skill helps you quickly load and apply work context from the Ravenclaw system.
First, get the full work context. If the Ravenclaw MCP server is available, use the get_work_context tool. Otherwise, run the CLI:
rc context
Check what's currently in progress:
rc issue list --status=in_progress --format=table
Check what's blocked or ready to start:
rc issue list --status=todo --format=table
If working on a specific issue, check for user comments/feedback:
rc comment list issue <issue-id>
Pick an issue to work on and mark it:
rc issue start <key>
Update the issue and add any relevant wiki documentation:
rc issue done <key>
rc wiki write <topic-slug>
Before starting work on an epic's issues, acquire a lock:
rc lock acquire <epic-id> --session $SESSION_ID --agent claude-code
Keep the lock alive during long work:
rc lock heartbeat <epic-id> --session $SESSION_ID
Release when done:
rc lock release <epic-id> --session $SESSION_ID
Or simply use rc issue start <key> — it auto-acquires the epic lock.
Check for existing locks:
rc lock list
rc context --compact for a token-efficient summaryrc search "keyword" to find relevant epics, issues, or wiki pages