2,282 件 ・ 関連度順
概要と使いどころ
Find new skills on GitHub or check a specific skill before installing. Use when the user wants to search for skills, evaluate a skill URL, check overlap and security risk before installing, or compare a local skill against alternatives. Trigger with '/janitor-discover'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.
日本語の概要は準備中です。原文の説明を表示しています。
CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.
日本語の概要は準備中です。原文の説明を表示しています。
CRE Retail analysis suite - 8 specialist skills for U.S. retail trade-area studies, rent roll and tenant mix, lease abstraction, co-tenancy and anchor risk, CAM recovery, underwriting, financing fit, and investment committee memo writing.
日本語の概要は準備中です。原文の説明を表示しています。
CRE Lender/Credit analysis suite - 8 specialist skills for U.S. CRE loan screening and sizing, sponsor and appraisal review, credit memo writing, annual risk rating, covenant and watchlist monitoring, problem loans, and portfolio stress testing.
日本語の概要は準備中です。原文の説明を表示しています。
Write a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any security review in code_review - risk-tier each changed file, read the repo's own security patterns, compare, then trace source to sink, including removed guards and blast radius
日本語の概要は準備中です。原文の説明を表示しています。
Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early
日本語の概要は準備中です。原文の説明を表示しています。
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Validate a startup idea with competitor analysis, market signals, and risk assessment. Be brutally honest. Use when the user wants to test if an idea is worth building.
日本語の概要は準備中です。原文の説明を表示しています。
用户准备做出一个重大决策（投资/收购/承诺），需要评估下行保护是否充足时。或在估值不确定时决定是否行动。 语言信号："这个价格够不够低"/"万一判断错了怎么办"/"我能承受多少亏损"/"下行空间有多大" 不适用于：日常低风险决策、纯上行分析（不关心下行保护时）。
日本語の概要は準備中です。原文の説明を表示しています。
用户考虑使用杠杆（保证金/贷款/融资）来放大投资回报，或评估财务安全性时。 语言信号:"要不要加杠杆"/"用保证金买""贷款投资划算吗"/"融资利率很低应该借钱投吗" 不适用于:不涉及杠杆/融资的纯经营决策。
日本語の概要は準備中です。原文の説明を表示しています。
Imagine the project has already shipped and failed catastrophically — work backwards from the failure to identify the most likely causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists.
日本語の概要は準備中です。原文の説明を表示しています。
Save checkpoints before risky changes. Rollback if things break.
日本語の概要は準備中です。原文の説明を表示しています。
Explores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or unclear request. Not for an already-scoped bug fix, an existing implementation plan, or a narrow code review.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares and controls software releases with risk classification, CI quality gates, artifact provenance, feature flags, staged rollout, measurable promotion and rollback thresholds, post-deploy verification, and cleanup. Use for deployment pipelines, launch readiness, canaries, production rollout, release automation, or rollback planning. Not for merely merging a completed development branch or proving one local change.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and manages isolated Git worktrees for parallel agents, risky experiments, or long-running feature work while preserving the user's current checkout. Use before concurrent branch edits or when isolation makes rollback safer. Not for a trivial one-file change that is already isolated.
日本語の概要は準備中です。原文の説明を表示しています。
Threat-models and hardens an application, API, data flow, dependency, or deployment against authentication and authorization flaws, injection, secrets exposure, unsafe deserialization, SSRF, abuse, privacy loss, and supply-chain risk. Use for security review, threat modeling, hardening, or sensitive changes. Not for generic code style review or an unexplained bug without a security hypothesis.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.
日本語の概要は準備中です。原文の説明を表示しています。
Selects and composes the Godmode skills for a coding task, explains the activation boundary, keeps workflow skills from being skipped when they materially reduce risk, and identifies the task's current engineering lifecycle state. Use when starting a task with Godmode installed, deciding which skill to invoke, recovering a task after context loss, or checking whether a workflow applies. Not a replacement for the selected skill's instructions or for repository-local rules.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.
日本語の概要は準備中です。原文の説明を表示しています。
Designs risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Guides user research and research ops. Use when running interviews, usability tests, surveys, or synthesis to de-risk product decisions; not experiments or review mining.
日本語の概要は準備中です。原文の説明を表示しています。