원클릭으로
status
Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Guide for safely discovering and installing skills from external repositories. Use when a user asks for something where a specialized skill likely exists (browser testing, PDF processing, document generation, etc.) and you want to bootstrap your understanding rather than starting from scratch.
Connect to MCP (Model Context Protocol) servers and create skills for repeated use. Load when a user wants to use an MCP server, connect to external tools via MCP, or when they mention MCP, model context protocol, or specific MCP servers.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations.
Decomposes and reorganizes agent memory blocks into focused, single-purpose components. Use when memory has large multi-topic blocks, redundancy, or poor organization.
Comprehensive guide for initializing or reorganizing agent memory. Load this skill when running /init, when the user asks you to set up your memory, or when you need guidance on creating effective memory files.
Send messages to other agents on your server. Use when you need to communicate with, query, or delegate tasks to another agent.
| name | status |
| description | Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks. |
| argument-hint | |
| user-invocable | true |
| allowed-tools | Bash |
Generate a comprehensive status report by running these commands:
!bd stats 2>/dev/null || echo "No beads stats available"
!bd list --status=in_progress 2>/dev/null || echo "No in-progress issues"
!bd blocked 2>/dev/null || echo "No blocked issues"
!bd ready 2>/dev/null || echo "No ready issues"
Summarize findings in this format:
[List in-progress issues with assignees]
[List blocked issues and what they're waiting on]
[List ready issues that can be picked up]
[Stats summary — open/closed/blocked counts]
[Suggested next actions based on current state]