メール、カレンダー、タスク管理、自動化（7,851 件）
Disciplined goal-to-execution workflow for any user task. Parses objective, asks only for materially missing requirements via ambiguity-gate, inspects repo via idea, plans via sdd-dev or deep-plan, executes safely under project conventions, verifies completion per R020, and reports changed files with evidence. Use when user invokes /goal <task>.
日本語の概要は準備中です。原文の説明を表示しています。
YAML-based DAG workflow engine with topological execution and failure strategies
日本語の概要は準備中です。原文の説明を表示しています。
Routes development tasks to the correct language or framework expert agent. Use when user requests code review, implementation, refactoring, or debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
日本語の概要は準備中です。原文の説明を表示しています。
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Write the spec before the code, then check the built thing against it — so agents build what was agreed, not what they invented.
日本語の概要は準備中です。原文の説明を表示しています。
Turn friction you just hit into a concrete change to the workflow, so the same problem doesn't recur.
日本語の概要は準備中です。原文の説明を表示しています。
Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.
日本語の概要は準備中です。原文の説明を表示しています。
Run independent, task-matched expert attempts, select a base, and synthesize the strongest result.
日本語の概要は準備中です。原文の説明を表示しています。
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
日本語の概要は準備中です。原文の説明を表示しています。
After a weekly report is built, diff it against the PRIOR report to find items that appear in BOTH weeks, then print the Owner (and prospect "Passed to") value recorded last week so it can be carried forward. Print-only — never edits the owner fields; Nathan verifies and re-tags in Notion. Invoked by weekly-report near the end, and standalone on "carry forward owners", "who owned this last week", "owner continuity".
日本語の概要は準備中です。原文の説明を表示しています。
Build the locked Slack TL;DR JSON payload from a completed weekly report. Saves to /tmp/slack-msg.json with the exact curl command for Nathan to post manually. Triggers on "draft Slack TL;DR", "Slack post", "build the Slack message".
日本語の概要は準備中です。原文の説明を表示しています。
Implement tasks from an OpenSpec change (Experimental)
日本語の概要は準備中です。原文の説明を表示しています。
Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.
日本語の概要は準備中です。原文の説明を表示しています。
Archive a completed change in the experimental workflow
日本語の概要は準備中です。原文の説明を表示しています。
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
日本語の概要は準備中です。原文の説明を表示しています。
On-demand "what's new" generator. Main context (which knows the impending change) writes keepachangelog-style entries to a fragment file at `.claude/state/whatsnew/<slug>.json` (gitignored, transient). An optional per-project `project.json → whatsnew.route_workflow` names a routing workflow that consumes the fragment and renders it wherever the project wants (a site page, a release body, a docs page). Not a workflow phase — it never blocks a commit, and it never writes `CHANGELOG.md` (that file is owned solely by semantic-release in CI).
日本語の概要は準備中です。原文の説明を表示しています。
Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an approved spec into a dependency-ordered swarm plan — one task per component, each with an explicit write_set. Produces `.claude/state/swarm/<slug>.json` with tasks + waves. The wave scheduler guarantees pairwise-disjoint write_sets within each wave so parallel dispatch is provably conflict-free.
日本語の概要は準備中です。原文の説明を表示しています。
Triage an incoming request — pick the workflow entry phase (intake / spec / tdd / chore) and record the workflow statefile that the Track Guard reads.
日本語の概要は準備中です。原文の説明を表示しています。
Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only view of the execution roadmap. Lists every epic with its per-status tallies, nests the still-open rows beneath their epic, collapses wholly-finished epics into one rollup line, and closes by naming the next planned task in file order. Four verbs — `list` (the reader's view), `tasks` and `epics` (filterable row and epic queries), `next` (the first planned task). Invoke any time to see what is left to build. Not a workflow phase; never writes; never starts or commits work.
日本語の概要は準備中です。原文の説明を表示しています。