936 件 ・ 関連度順
概要と使いどころ
Assess agentic layer maturity using the 12-grade classification system (Class 1-3). Use when evaluating codebase readiness, identifying next upgrade steps, or tracking progress toward the Codebase Singularity.
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage AI agent skills following best practices. Use when creating new skills, optimizing context, designing multi-agent systems, or implementing progressive disclosure patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via /spawn command. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks
日本語の概要は準備中です。原文の説明を表示しています。
Generate markdown reports from issues. Filter by type, priority, epic, date range. Supports summary, detailed, progress, completion, velocity, and backlog analysis views.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Run a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.
日本語の概要は準備中です。原文の説明を表示しています。
Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).
日本語の概要は準備中です。原文の説明を表示しています。
Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Execute Anarlog work immediately while recording issues, decisions, progress, and lessons in Linear. Use for Anarlog repository or Anarlog desktop, web, mobile, and API work, including related worktrees and ANLG issues. Explicit brainstorming stays discussion-first. Do not use for unrelated repositories or meeting-data queries.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-issue → oss-contribute chain for that.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.
日本語の概要は準備中です。原文の説明を表示しています。
Prompt engineering standards and context engineering principles for AI agents based on Anthropic best practices. Covers clarity, structure, progressive discovery, and optimization for signal-to-noise ratio.
日本語の概要は準備中です。原文の説明を表示しています。
Create a GitHub issue, assign to current user, and set status to In Progress
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks about evolution progress, current scores, best version, how many iterations ran, or whether the loop is stagnating.
日本語の概要は準備中です。原文の説明を表示しています。
Run the full content pipeline in one command — brief, write, gate, log. Progress updates between steps. 5-minute timeout with partial state recovery.
日本語の概要は準備中です。原文の説明を表示しています。
Session wrap-up: consolidates every descriptive markdown file (README.md, AGENTS.md, HANDOFF.md, docs/*) into ONE canonical CLAUDE.md, then reconciles it against the current code state so a fresh session or new teammate can pick up immediately. CLAUDE.md keeps a mandatory PROGRESS block at the top answering two questions: where are we now and what's the next concrete action. Trigger when the user says: "wrap", "wrap up", "/wrap", "tidy docs", "sync docs", "update docs", "archive", "this phase is done", or the Chinese equivalents "收尾", "同步文档", "整理文档", "整理一下", "更新文档", "存档", "梳理一下", "这阶段做完了". A bare "tidy" / "整理" with prior dev context counts. Do not under-trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
设计发布策略时使用。适用于灰度 / 蓝绿 / 金丝雀 / 滚动更新 / 回滚方案。融合 Progressive Delivery + Feature Flags + 自动回滚。
日本語の概要は準備中です。原文の説明を表示しています。
追踪项目进度和处理阻塞时使用。适用于项目执行阶段、定期状态汇报、阻塞升级。优先使用任务状态机 + 三级阻塞升级 + 进度摘要格式。
日本語の概要は準備中です。原文の説明を表示しています。
Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only.
日本語の概要は準備中です。原文の説明を表示しています。
Skill Chain Engine — compose skills into automated pipelines. One task triggers multi-skill workflows with progress tracking, auto-detection, and step management.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running ANY terminal command - enforces clear progress logging, output reading, and error-stop behavior so terminal processes are never left unchecked
日本語の概要は準備中です。原文の説明を表示しています。
Strategic codebase re-direction when requirements change, architecture doesn't fit, or tech debt blocks progress. TRIZ-powered pivot protocol for large codebases.
日本語の概要は準備中です。原文の説明を表示しています。
View a quick progress summary of current tasks.
日本語の概要は準備中です。原文の説明を表示しています。