Productivity skills

ブランチ作成、コミット、PR作成までのGitワークフローを支援する

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks to "create a team", "spawn agents", "parallel execution", "delegate tasks to agents", "use a swarm", "team workflow", "split work across agents", "run tasks in parallel", or mentions wanting multiple agents to collaborate on a complex task.

The English summary is being prepared. Showing the original description.

実装計画・設計書からタスクを分解し、ファイル単位の依存関係を分析して 並列実行可能な Wave に自動グルーピングするスキル。 編集ファイルが被らないタスクは全て同時並列にし、 Mermaid 依存関係図 + ディレクトリ分割された TODO ファイル群を出力する。 team-plan の後工程、team-implement の前工程として使える。 Use when: 実装計画を並列タスクに分解したい、Wave 実行順序を設計したい、 タスクの依存関係を可視化したい、分業できる部分を洗い出したい。 Triggers: "タスク分解", "並列タスク", "parallel task", "Wave 設計", "依存関係を整理", "分業", "タスクリスト作成", "並列計画", "task breakdown", "parallel plan", "wave planning", "同時に進められる"

The English summary is being prepared. Showing the original description.

Set up Fastlane for iOS/macOS app automation

The English summary is being prepared. Showing the original description.

Apply the Minimum Sufficient Language (MSL) principle through the MSL Kernel to write anything a reader must act on. Bind the reader and what they already know, partition facts from the machinery that produced them, emit each admitted fact as an action, a verification, a judgment, or a state, and stop when every claim is checkable and the reader can act. Use for status updates, work-in-progress reports to your own user, closeout and convergence comments, tickets, pull request and review write-ups, incident and postmortem notes, emails, memos, and any draft for readers outside the work. Also use when the user says MSL, Minimum Sufficient Language, write this for stakeholders, drop the jargon, make this readable, or asks for a paste-ready draft.

The English summary is being prepared. Showing the original description.

Run an authorized task inside an Available Work Time (AWT) window with a shorter Closeout Grace Period (CGP), fixed deadlines, forecast checks, proportional convergence points, and a hard stop. Use when the user explicitly requests timeboxing, supplies an AWT/CGP pair, says AWT or CGP, or an applicable project policy requires the protocol. Do not invent durations or activate timeboxing merely because a task may take time.

The English summary is being prepared. Showing the original description.

Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool integrations.

The English summary is being prepared. Showing the original description.

Meta-agent supervisor that manages a fleet of Claude Code agents running in tmux windows. Auto-discovers spare worktrees, spawns agents, monitors state, kicks idle agents, approves safe confirmations, and recycles worktrees when done. TRIGGER when user asks to supervise agents, run parallel tasks, manage worktrees, check agent status, or orchestrate parallel work.

The English summary is being prepared. Showing the original description.

Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".

The English summary is being prepared. Showing the original description.

Use when creating FreeRTOS tasks, queues, semaphores, or mutexes, catching stack overflow, writing FreeRTOSConfig.h, or debugging tasks over OpenOCD and GDB. Not for probe setup: use openocd-jtag.

The English summary is being prepared. Showing the original description.

Use when authorized workflow history may contain a repeated process worth extracting and replay-testing. Produces a contradiction-tested workflow mined from authorized history.

The English summary is being prepared. Showing the original description.

Use when the user wants to be walked through code, not handed a report: "walk through this", "guided code walk", or "explain this codebase". Not for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.

The English summary is being prepared. Showing the original description.

Use when a user asks to mine recent chats for workflow preferences. Don't use for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the user says "wait, what", "the explanation is unclear", "say that again", or asks to restate the last response in plain language. Not for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.

The English summary is being prepared. Showing the original description.

Use when filing an approved task spec as a GitHub issue with a local archive and optional worktree implementer. Don't use for spec drafting without human interrogation and redaction gates.

The English summary is being prepared. Showing the original description.

Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

The English summary is being prepared. Showing the original description.

Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.

The English summary is being prepared. Showing the original description.

Use when a human explicitly requests the daily on-call issue digest from a named issue tracker for a configured Slack channel. Not for posting without explicit human authorization for that run.

The English summary is being prepared. Showing the original description.

Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.

The English summary is being prepared. Showing the original description.

Use when a proof needs Isabelle/HOL, its Sledgehammer automation, or an AFP session. Not for Lean 4: use writing-lean-proofs.

The English summary is being prepared. Showing the original description.

Use when work is about to grow past the ask, the task may already be done, or the user requests only the minimum. Not for executing the work: use tdd to build or strike-the-root to fix.

The English summary is being prepared. Showing the original description.

Use when a task, feature, or fix is called done, complete, finished, or fixed, or before a commit, PR, or next task. Not for fact-checking: use verify-both-ways. Not for measuring: use verify-this.

The English summary is being prepared. Showing the original description.