8,237 件 ・ 関連度順
概要と使いどころ
Plan shoot-ready Amazon product photography, listing image sets, infographics, lifestyle scenes, and production briefs. Use when a seller asks for an Amazon photo shot list, creative direction, image-pack plan, photography budget, DIY-versus-done-for-you decision, or handoff to a photographer or image-generation workflow. Do not use for listing copy or image-only performance auditing.
日本語の概要は準備中です。原文の説明を表示しています。
Seasonal sales calendar — Prime Day, Black Friday, Q4 prep, inventory planning, promotion scheduling
日本語の概要は準備中です。原文の説明を表示しています。
Build a product-specific Amazon FBA prep, labeling, packing, and shipment-readiness plan. Use when a seller asks how to prepare units for FBA, choose barcode and labeling steps, plan poly-bagging, bubble wrap, sets, case packs, cartons, dangerous-goods review, supplier or prep-center instructions, or prevent receiving delays. Do not use as a substitute for current Seller Central requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Decides whether a company publishes public self-serve pricing and extracts its plan tiers, price points and feature axis. Triggers on "do they have a pricing page", "is their pricing public", "filter out enterprise quote-only companies", "what do they charge", "find their plans", "self-serve vs sales-led". Outputs a structured pricing record per domain. The copy-ready pricing clause is OFF by default and runs only when a campaign brief asks for it.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute a new brand launch — from internal rollout to public debut. Use when the user says "launch the brand", "brand launch plan", "how do we introduce the brand", "brand reveal", "brand debut", "going public with the brand", "announcing the new brand", "brand launch strategy", "pre-launch brand", "brand rollout", "introducing our brand to the market", or is ready to take a new or refreshed brand from internal to external. Also use for soft launches, hard launches, and phased rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a completed task, browser flow, artifact pipeline, failure-recovery trace, or repeatedly refined workflow into a new reusable skill package or a reviewed skill-design plan. Use when the user asks to make a new skill from real run history, extract a reusable workflow from conversation/logs/files, summarize lessons into a new skill, or produce a plan before writing files. Do not use to upgrade an existing skill or to execute the business workflow itself.
日本語の概要は準備中です。原文の説明を表示しています。
Split the Plan/Act/Verify loop across three model tiers — frontier planner, cheap executor, frontier judge — via env vars read by run.sh.
日本語の概要は準備中です。原文の説明を表示しています。
Execute detailed plans in batches with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
日本語の概要は準備中です。原文の説明を表示しています。
Map 50-200+ keywords into topical clusters for SEO domination. Build content roadmaps for topical authority. Triggers on: "keyword research", "keyword clustering", "topical authority", "keyword map", "keyword strategy", "content roadmap for SEO", "keyword grouping", "topic clusters", "SEO keyword plan", "map my keywords", "keyword cluster", "hub and spoke content", "build topical authority", "SEO content plan", "keyword universe".
日本語の概要は準備中です。原文の説明を表示しています。
Turn a feature request into a minimal, file-level implementation plan before any code.
日本語の概要は準備中です。原文の説明を表示しています。
Deutsche Bahn train schedules, journey planning, and departures across Germany and into neighboring countries (Austria, Switzerland, Netherlands, France, Belgium). Use for ICE/IC/regional rail planning and airport ground transport (FRA, MUC).
日本語の概要は準備中です。原文の説明を表示しています。
Review and revise academic papers with a senior-reviewer workflow. Use when an AI research/coding agent needs to work on an existing paper draft, PDF, LaTeX project, Word document, markdown manuscript, rejected paper, or paper idea that already has a concrete direction, and produce: paper maps, weakness audits, insight/novelty checks, reviewer objections, claim-experiment matrices, theory/proof checks, experiment plans, statistics/reproducibility audits, figure/table audits, ethics/compliance checks, revision plans, detailed section edits, or final submission checklists.
日本語の概要は準備中です。原文の説明を表示しています。
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a Harness Engineering framework in the current project. Use when user says 'harness', 'init harness', 'initialize framework', 'setup harness engineering', '/harness', or wants to set up a Plan-Build-Verify development workflow with specialized agents (planner, generator, evaluator). Creates CLAUDE.md, agent definitions, command templates, hooks, and documentation structure for autonomous AI-driven development.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a phase plan should be peer-reviewed by other AI CLIs before execution, or the user asks for a cross-AI review. Invokes Gemini, Claude, Codex, or OpenCode and writes REVIEWS.md for /gsd-plan-phase --reviews.
日本語の概要は準備中です。原文の説明を表示しています。
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 for a trivial task the user can describe in one sentence: a typo, config change, small refactor or forgotten commit. Executes inline with no subagents and no PLAN.md; anything needing research or planning belongs to /gsd-quick.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting GSD in a repo that has no .planning/ yet, or the user wants a new project set up. Questioning, optional research, requirements, and roadmap produce .planning/PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what the codebase intel knows, or runs /gsd-intel query, status, diff, or refresh. Queries or rebuilds the .planning/intel/ files, and stops with a disabled message when intel is off in .planning/config.json.
日本語の概要は準備中です。原文の説明を表示しています。
Use when opening a pull request and the diff is cluttered with .planning/ commits. Creates a clean branch filtered of GSD planning artifacts so reviewers see only code changes.
日本語の概要は準備中です。原文の説明を表示しています。
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 when a milestone audit reported gaps and you want the fix phases created in one pass. Reads MILESTONE-AUDIT.md, groups gaps into phases, adds them to ROADMAP.md and offers to plan each one.
日本語の概要は準備中です。原文の説明を表示しています。