Produce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation planning workflow using the plan template to generate design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
General code quality review — project guideline compliance, bug detection, code quality analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Code comment accuracy verification, documentation completeness assessment, comment rot detection.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update the feature specification from a natural language feature description.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
日本語の概要は準備中です。原文の説明を表示しています。
Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
日本語の概要は準備中です。原文の説明を表示しています。
Shared in-workflow quality gates for code/PR skills — the gate model, trust tiers, and the three primitives (evidence-before-done, independent judge, anti-gaming). DO NOT TRIGGER directly — referenced by consumer skills via relative path.
日本語の概要は準備中です。原文の説明を表示しています。
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh the managed Spec Kit section in coding agent context file(s)
日本語の概要は準備中です。原文の説明を表示しています。
Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-commit changes after a Spec Kit command completes
日本語の概要は準備中です。原文の説明を表示しています。
Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
日本語の概要は準備中です。原文の説明を表示しています。
Error handling review — silent failure detection, catch block analysis, error logging.
日本語の概要は準備中です。原文の説明を表示しています。
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
日本語の概要は準備中です。原文の説明を表示しています。