346 件 ・ 関連度順
概要と使いどころ
The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Semantic code search using Phase 1 vector embeddings and Phase 2 hybrid search.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 2 of 5 — collaborative system design plus change-footprint mapping; outputs an ARCH doc for generate-tasks. Use only when the user asks to run Phase 2, plan the architecture, or design the solution — never trigger automatically from a design question.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 4 of 5 — implements tasks from TASKS-<N>-<slug>.md (with ARCH-<N>-<slug>.md as architecture-only context) using mode-appropriate verification (tdd, test-after, ui, checklist); pass 'auto' to run without stepping. Use only when the user asks to run Phase 4 or implement tasks from an ARCH doc — never trigger automatically from a coding request.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS-<N>-<slug>.md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
日本語の概要は準備中です。原文の説明を表示しています。
研究编辑（季要纲 Ji）。由 research-chief-editor 主理人调度，分析 Phase 1 初步调研摘要，提取核心观点，确定报告标题，规划章节大纲（3-5 章），管理章节不重叠、逻辑递进。也负责根据用户反馈修改大纲。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 2 规划任务时激活。
日本語の概要は準備中です。原文の説明を表示しています。
报告发布员（傅梓铭 Fu）。由 research-chief-editor 主理人在 Phase 5 调度，整合所有部分（标题/日期/目录/引言/章节正文/结论/参考文献/审稿警告）输出最终 Markdown 研究报告。执行终校：格式统一、章节编号连续、分隔线、超链接检查、参考文献去重、术语一致性检查。不修改研究内容本身。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当 Phase 4 完成后，主理人下发 Phase 5 发布任务时激活。
日本語の概要は準備中です。原文の説明を表示しています。
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).
日本語の概要は準備中です。原文の説明を表示しています。
Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.
日本語の概要は準備中です。原文の説明を表示しています。
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)
日本語の概要は準備中です。原文の説明を表示しています。
長いClaude Codeの作業で、会話や読み込んだ情報を圧縮するタイミングを提案します。文脈量とツール呼び出し回数を目安に、工程の区切りで重要な計画を残す判断を支援します。
まだ存在しない機能の追加を、調査・計画からテスト先行の実装、レビュー、コミットまで進めるスキル。工程を担当エージェントに分担し、計画とコミット前に承認を挟みます。
Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multi-phase deep research with web search, memory retrieval, pattern matching, and synthesis into structured findings
日本語の概要は準備中です。原文の説明を表示しています。
VS-Enhanced Literature Review Strategist - Comprehensive support for multiple review methodologies Full VS 5-Phase process: Prevents Mode Collapse and presents creative search strategies Supports: Systematic Review (PRISMA 2020), Scoping Review (JBI/PRISMA-ScR), Meta-Synthesis, Realist Synthesis, Narrative Review, Rapid Review Use when: conducting any type of literature review, systematic reviews, meta-analyses, scoping reviews, finding prior research Triggers: literature review, PRISMA, systematic review, scoping review, meta-synthesis, realist synthesis, narrative review, rapid review
日本語の概要は準備中です。原文の説明を表示しています。
Detect insecure JWT (JSON Web Token) implementations in a codebase using a two-phase approach: first map all JWT issuance and verification sites to understand the token lifecycle and signing configuration, then check each verification site for exploitable weaknesses such as algorithm confusion, missing signature verification, weak secrets, header injection, and missing claim validation. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/jwt-results.md. If no JWT usage is found in Phase 1, Phase 2 is skipped. Use when asked to find JWT, token forgery, or authentication bypass bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Detect GraphQL injection vulnerabilities in a codebase using a three-phase approach: recon (confirm GraphQL usage and find unsafe operation document assembly sites), batched verify (trace user input to those sites in parallel subagents, up to 3 candidate sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/graphql-results.md. If no GraphQL technology is found in Phase 1, later phases are skipped. Use when asked to find GraphQL injection, unsafe GraphQL document construction, or operation string injection bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Perform codebase analysis and architecture mapping as the first phase of a security assessment. Explores the tech stack, frameworks, entry points, data flows, and trust boundaries. Outputs sast/architecture.md. Run this before any vulnerability detection skill. Use when asked to analyze a codebase for security or when sast/architecture.md does not yet exist.
日本語の概要は準備中です。原文の説明を表示しています。
Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase.
日本語の概要は準備中です。原文の説明を表示しています。
Use to re-verify the threat mitigations of a phase that already shipped, or when the user asks to audit SECURITY.md. Audits an existing SECURITY.md, runs from a PLAN.md threat model, or exits if the phase never ran.
日本語の概要は準備中です。原文の説明を表示しています。
Use when .planning/phases/ has accumulated directories from completed milestones. Shows a dry-run of what moves to .planning/milestones/v{X.Y}-phases/ and archives only after confirmation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to execute a phase's plans, resume the remaining plans, or run only one wave. Discovers plans, groups them into dependency waves, spawns a fresh subagent per plan, then verifies the phase.
日本語の概要は準備中です。原文の説明を表示しています。