1,025 件 ・ 関連度順
概要と使いどころ
Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.
日本語の概要は準備中です。原文の説明を表示しています。
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls.
日本語の概要は準備中です。原文の説明を表示しています。
Display project statistics — phases, plans, requirements, git metrics, and timeline
日本語の概要は準備中です。原文の説明を表示しています。
Request cross-AI peer review of phase plans from external AI CLIs
日本語の概要は準備中です。原文の説明を表示しています。
Socratic ideation and idea routing — think through ideas before committing to plans
日本語の概要は準備中です。原文の説明を表示しています。
Execute all plans in a phase with wave-based parallelization
日本語の概要は準備中です。原文の説明を表示しています。
Ingest external plans with conflict detection against project decisions before writing anything.
日本語の概要は準備中です。原文の説明を表示しています。
Govern mini-program release readiness and evidence across source branches, semantic versions, build artifacts, test flags, debug paths, sensitive data, permissions, privacy declarations, platform uploads, review submissions, staged versions, production releases, and rollback plans. Use when users ask for a release checklist, packaging, export, version bump, upload readiness, submission readiness, launch status, rollback preparation, or a precise judgment of what has and has not shipped. Defaults to read-only preflight, requires separate explicit authorization for every external state change, and never treats a Git push, successful build, platform upload, review submission, approval, or production publication as interchangeable.
日本語の概要は準備中です。原文の説明を表示しています。
Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.
日本語の概要は準備中です。原文の説明を表示しています。
Clerk authentication router. Use when user asks about Clerk CLI operations, adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, React patterns, Vue patterns, Nuxt patterns, Astro patterns, TanStack Start patterns, Expo patterns, React Router patterns, Chrome Extension patterns, organizations, billing, subscriptions, payments, pricing, plans, seat-based pricing, feature entitlements, syncing users, or testing. Automatically routes to the specific skill based on their task.
日本語の概要は準備中です。原文の説明を表示しています。
仅计划模式——在 `plans/` 下编写可执行的 markdown 计划，不执行。 当用户输入 /plan 或明确要求计划而非实现时触发。
日本語の概要は準備中です。原文の説明を表示しています。
Plan mode only — write an actionable markdown plan under `plans/`, no execution. Bite-sized tasks, exact paths, complete code. Trigger when the user wants a plan instead of implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
日本語の概要は準備中です。原文の説明を表示しています。
Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.
日本語の概要は準備中です。原文の説明を表示しています。
Review implementation plans for parallelization, TDD, types, libraries, and security before execution
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes and compares health insurance plans (individual vs group), calculates costs, verifies networks, and generates formatted comparison reports for decision-making
日本語の概要は準備中です。原文の説明を表示しています。
Create marketing plans for insurance agencies. TRIGGERS - Use when user needs help with insurance-marketing-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Design agency perpetuation plans. TRIGGERS - Use when user needs help with insurance-perpetuation-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Compare health insurance plans, estimate total yearly costs, and choose coverage that fits medical usage, prescriptions, and financial risk.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing clinical notes, documenting sessions, creating treatment plans for insurance/authorization, ensuring HIPAA compliance, or need structured documentation templates. Provides SOAP notes, progress notes (DAP format), and treatment plan templates. HIPAA-compliant guidance included.
日本語の概要は準備中です。原文の説明を表示しています。
Writes employee benefits guides explaining health insurance, retirement plans, PTO, and perks in plain language. Use when onboarding new hires or updating benefits documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".
日本語の概要は準備中です。原文の説明を表示しています。
Turn Markdown outlines, notes, docs, or plans into an interactive mind map — a single self-contained HTML file that opens offline anywhere (markmap.js, white-on-dark, zoom/expand/export toolbar, search that keeps matches in context). Use whenever the user asks for a mind map, markmap, or concept map, wants to visualize or diagram the structure of a document or topic, summarize notes as a navigable tree, make an outline clickable or explorable, or embed such a map in Streamlit — even when they don't literally say 'mind map'.
日本語の概要は準備中です。原文の説明を表示しています。