メニュー
Use when the user wants every response to end with a clear status signal — "give me a status line", "use the red/yellow/green convention", "end with a recap" — or when installing the managed AGENTS.md/CLAUDE.md status-block instruction.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
The autonomous-sdlc state machine. Loaded by every /sdlc loop iteration to decide what one unit of work the current state requires, how to verify it, and which transition to record. Trigger: an active `.sdlc/state.json` exists, or the /sdlc command invokes it. Not for ad-hoc use outside a loop.
Save agent-skills workflow feedback proactively. MUST trigger when the user corrects how a visual plan/recap, recap status block, orchestration, autonomy, docs-first, or review skill behaves ("recaps are too long", "always web-search the docs first", "don't stop to ask", "plans should lead with the wireframe") or confirms good output. Also trigger on explicit requests: "save this feedback", "show my feedback", "clear feedback", "agent-skills preferences", "consolidate feedback", "bake in my preferences". Feedback loaded automatically when running these skills.
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a session ID, Claude Code session/transcript, PR, branch, log, or run summary.
Use always when operating as Claude Fable on codebase-heavy or token-heavy work: Fable orchestrates, architects, synthesizes, and judges while cheaper subagents do bounded research, coding, testing, and log reduction.
Use whenever running a high-cost frontier model on codebase-heavy or token-heavy work (apply automatically on such models): delegate research, coding, testing, and log reduction to cheaper subagents, reserving the expensive model for planning, tradeoffs, synthesis, and final review.
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies.
| name | quick-recap |
| description | Use when the user wants every response to end with a clear status signal — "give me a status line", "use the red/yellow/green convention", "end with a recap" — or when installing the managed AGENTS.md/CLAUDE.md status-block instruction. |
Make completion state obvious at the end of every response.
Every response that completes a unit of work must end with:
🟢 Actual concise status sentence
Rules:
🟢 when the requested work is finished.🟡 when non-routine follow-up remains; name the pending item.🔴 only when blocked on user input.---, spacer lines, or any content after the status line.This convention is only automatic when it is present in project or user
instructions. When installing this skill, prefer adding the managed
AGENTS.md / CLAUDE.md block unless the user opts out.
If you are following the convention manually, choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked.
Finished work:
🟢 Updated quick recap docs with output examples
Non-routine follow-up remains:
🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
Blocked on user input:
🔴 Need the production API key to continue