メニュー
Daily standup summary — what was completed recently, what's in progress, and what's blocked. Use when the user asks for a standup, status update, or summary of recent work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Prepare a session handoff — summarize progress, annotate tasks with current status, and identify what's ready for the next session. Use at the end of a work session or when the user says they're done for now.
Pick up a task from the backlog and implement it. Reads the spec if one exists, starts the task, does the work, and marks it done. Use when the user wants to work on a specific task or the next available task.
Break down a goal into actionable tasks with dependencies, priorities, and optional specs. Use when the user wants to plan work, decompose a feature, or create a task breakdown.
Review and improve the backlog — identify vague tasks, missing priorities, broken dependencies, tasks needing specs, and stale items. Use when the user wants to groom, refine, clean up, or improve their task backlog.
Write a detailed spec document for a task before implementation begins. Use when the user wants to define requirements, acceptance criteria, or technical design for a task.
Show the current task backlog — pending, active, blocked, and overdue tasks. Use when the user asks about tasks, status, what needs to be done, or what's in progress.
| name | standup |
| description | Daily standup summary — what was completed recently, what's in progress, and what's blocked. Use when the user asks for a standup, status update, or summary of recent work. |
Generate a concise standup report by querying the backlog.
Done — call task_list with filter status:completed end.after:now-1d to show tasks completed in the last 24 hours. If empty, try end.after:now-7d for the last week.
In progress — call task_list with filter +ACTIVE to show tasks currently being worked on.
Blocked — call task_list with filter +BLOCKED status:pending to show tasks waiting on dependencies. For each, identify which task is blocking it.
Up next — call task_list with filter status:pending and pick the top 3 by urgency that are NOT blocked. These are what should be worked on next.
Overdue — call task_count with filter +OVERDUE to flag any overdue tasks.
Present as a brief, scannable report:
**Done**: [completed tasks or "nothing recent"]
**In progress**: [active tasks or "nothing started"]
**Blocked**: [blocked tasks and what's blocking them, or "none"]
**Up next**: [top 3 actionable tasks by urgency]
**Overdue**: [count, or skip if 0]
Keep it concise — this is a quick status check, not a full report. Skip sections that are empty.