7,591 件 ・ 人気順
概要と使いどころ
Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Sends the file's text to the configured model provider. Trigger: /caveman-compress.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task feels too large or vague to start, a spec needs breaking into implementable units, work must be parallelized across agents or sessions, or implementation order is unclear. Produces ordered tasks with acceptance criteria. Skip when the spec already contains well-defined tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Use on every code change — commit structure, branching, history hygiene, and versioning. Apply when committing work, opening or splitting a branch, writing commit messages, cutting a release, or recovering from a bad history state.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a project's CI pipeline, adding or changing automated checks, configuring deployment pipelines, or debugging CI failures. Covers quality gates, pipeline stages, and what to verify automatically on every change.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite Dart SDK skill. Use when building Flutter apps (mobile, web, desktop) or server-side Dart applications with Appwrite. Covers client-side auth (email, OAuth), database queries, file uploads with native file handling, real-time subscriptions, and server-side admin via API keys for user management, database administration, storage, and functions.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite Kotlin SDK skill. Use when building native Android apps or server-side Kotlin/JVM backends with Appwrite. Covers client-side auth (email, OAuth with Activity integration), database queries, file uploads, real-time subscriptions with coroutine support, and server-side admin via API keys for user management, database administration, storage, and functions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a daily "where are we?" digest from this repo's GitHub epics — a render-only HTML + plain-text email summarising the last 24h of activity plus a progress snapshot of every open epic. Use when asked for a "daily digest", "epic report", "status rapport", "what moved this week", or "where are we on the epics".
日本語の概要は準備中です。原文の説明を表示しています。
Turn one task into a tree of GitHub issues worked by agents. Creates (or reuses) an epic issue, then launches the recursive orchestrator → decomposer → worker pipeline. Use when asked to "decompose a task", "break this down into issues and work it", "spawn agents to build X", or run via /task-decompose.
日本語の概要は準備中です。原文の説明を表示しています。
A pessimistic go/no-go the moment you pick up a GitHub issue — read it skeptically and hunt for reasons NOT to do it (already done? obsolete? duplicate? premise wrong? cheaper way? net-negative?), returning proceed / reshape / drop with one-line evidence. The pickup-time half of the dedup gate (the create-time half is /issue-dedup). Use as step 1 of the Task Execution Workflow, or run /issue-sanity-check
日本語の概要は準備中です。原文の説明を表示しています。
Track work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".
日本語の概要は準備中です。原文の説明を表示しています。
Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Act on the queued items. Works through every pending item on the working todo list (the queue built with /list), actually doing each one, marking it in_progress then completed as you go. Use after stacking items with /list.
日本語の概要は準備中です。原文の説明を表示しています。
Queue an item WITHOUT acting on it. Appends the provided text as a new pending item on the working todo list, then stops. Use /list <text> to stack up tasks or notes one at a time; act on them later with /go. Does not plan or start the work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, testing, or updating active-recall flashcards grounded in session concepts to reinforce retention.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a learner needs a structured review session prioritizing high-value topics by recency, error history, and upcoming deadlines.
日本語の概要は準備中です。原文の説明を表示しています。
Use when scheduling and executing review sessions at scientifically-calibrated expanding intervals for long-term retention.
日本語の概要は準備中です。原文の説明を表示しています。
dev-graph の1 featureを exact 13 task specsへ分解したいとき、独立評価後に13-entry inventory・13-node DAGを atomic promotionしたいときに使う。
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
日本語の概要は準備中です。原文の説明を表示しています。
非エンジニアからスキル要件を引き出したいとき、manifest 駆動で要件書（intake）と Notion ページを生成したいときに使う。
intake 成果物を Notion へ初回公開したいとき、ヒアリングをやり直さず Notion 側だけ更新して再公開したいときに使う。
進行中のskill intakeのphaseと5軸を確認したいとき、visualとNotion公開状態をread-onlyで確認したいときに使う。
プラグイン構想から index+13 フェーズファイル+component-inventory.json とタスク粒度の型付き依存グラフ (task-graph) を第3の射影として生成したいとき、後段のrun-skill-createへ渡す前段の開発計画を立て build 中の discovered-task を --mode update の外ループで graph へ還流したいときに使う。
タスク仕様書ドメイン用L1 rubricを参照したいとき、Phase 1-13/SRP/ユビキタス言語の評価基準を確認したいときに使う。