936 件 ・ 関連度順
概要と使いどころ
Use when the user runs /gsd-workstreams or asks to list, create, switch, status, progress, complete, or resume parallel workstreams for concurrent milestone work. The active one is tracked in the GSD_WS variable.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks where the project stands, what to do next, or to resume after a break. Summarizes recent work and what is ahead, then routes to executing an existing plan or planning the next one.
日本語の概要は準備中です。原文の説明を表示しています。
Use to keep moving without inspecting progress, or when the user asks what is next in the GSD workflow. Reads STATE.md, ROADMAP.md and phase dirs to invoke the next step; --force skips safety and verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to create, scaffold, update or package a skill, or asks how skill frontmatter, progressive disclosure or bundled resources should be structured. Walks through init_skill.py, writing SKILL.md and package_skill.py.
日本語の概要は準備中です。原文の説明を表示しています。
Design or revise concise skills with clear triggers, proportional constraints, progressive disclosure, and realistic validation.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides. Use when conflict markers or an interrupted merge/rebase need investigation and resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
日本語の概要は準備中です。原文の説明を表示しています。
Review a Git diff against repository standards and its originating requirements. Use for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.
日本語の概要は準備中です。原文の説明を表示しています。
Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on "design workflow skill", "create workflow skill", "workflow skill designer".
日本語の概要は準備中です。原文の説明を表示しています。
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
日本語の概要は準備中です。原文の説明を表示しています。
Execute Elixir/Phoenix plan tasks with progress tracking. Use after $elixir-phoenix:phx-plan to implement features…
日本語の概要は準備中です。原文の説明を表示しています。
Execute Elixir/Phoenix plan tasks with progress tracking. Use after phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
日本語の概要は準備中です。原文の説明を表示しています。
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md findings. Use periodically for progress tracking.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used only when the user explicitly asks to use `$ralph-specum-status`, or explicitly asks Ralph Specum in Codex for status or active spec progress.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage todo tracking documents for features, bugs, and multi-step tasks. Use when starting new work that benefits from a persistent record of decisions, progress, and context.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive R package for command-line interface styling, semantic messaging, and user communication. Use this skill when working with R code that needs to: (1) Format console output with inline markup and colors, (2) Display errors, warnings, or messages with cli_abort/cli_warn/cli_inform, (3) Show progress indicators for long-running operations, (4) Create semantic CLI elements (headers, lists, alerts, code blocks), (5) Apply themes and customize output styling, (6) Handle pluralization in user-facing text, (7) Work with ANSI strings, hyperlinks, or custom containers. Also use when migrating from base R message/warning/stop, debugging cli code, or improving existing cli usage.
日本語の概要は準備中です。原文の説明を表示しています。
Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates implementation of a plan file by delegating work to subagents in parallel. Verifies git branch state, tracks progress, and ensures high-quality implementation. Invoke with a plan file path and optional model override: /implement plans/my-plan.md [--model sonnet]
日本語の概要は準備中です。原文の説明を表示しています。
Metacognitive check-ins during problem solving - detects when to pivot or persist
日本語の概要は準備中です。原文の説明を表示しています。
Pattern for progressively refining context retrieval to solve the subagent context problem
日本語の概要は準備中です。原文の説明を表示しています。