「planning」の検索結果

Seasonal sales calendar — Prime Day, Black Friday, Q4 prep, inventory planning, promotion scheduling

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Use when a marketing BUDGET has to be planned or managed in USD — allocation by bucket, channel, and month, test versus scale split, scale-up and stop-loss thresholds, reserve, a plan-versus-actual tracker, and a review cadence. Trigger on 'budget planning', 'marketing budget', 'split the budget across channels', 'stop loss threshold', 'quarterly budget', 'we keep overspending and nobody notices'. Also use when a number has been approved and nobody has divided it up. Not for — the revenue-backward math that produces the number, see `10-reverse-kpi-global`; paid media allocation only, see `54-media-plan-global`; paying an external vendor, see `67-agency-vendor-brief-global`.

日本語の概要は準備中です。原文の説明を表示しています。

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 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 .planning/ looks inconsistent, files are missing, or state seems wrong. Validates .planning/ integrity, reports missing files, bad config, and orphaned plans, and --repair fixes what it finds.

日本語の概要は準備中です。原文の説明を表示しています。

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 .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 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.

日本語の概要は準備中です。原文の説明を表示しています。

Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.

日本語の概要は準備中です。原文の説明を表示しています。

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

日本語の概要は準備中です。原文の説明を表示しています。

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.

日本語の概要は準備中です。原文の説明を表示しています。

Design and implement disaster recovery strategies with RTO/RPO planning, database backups, Kubernetes DR, cross-region replication, and chaos engineering testing. Use when implementing backup systems, configuring point-in-time recovery, setting up multi-region failover, or validating DR procedures.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain classic ASP.NET applications on .NET Framework, including Web Forms, older MVC, and legacy hosting patterns, while planning realistic modernization boundaries. USE FOR: working in Web Forms, legacy MVC, or classic ASP.NET applications; reviewing old IIS-centric configuration and lifecycle behavior; planning migration toward ASP.NET Core. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

日本語の概要は準備中です。原文の説明を表示しています。

Authorized red team engagement planning, C2 architecture design, attack methodology, lateral movement strategy, OPSEC, and professional reporting

日本語の概要は準備中です。原文の説明を表示しています。

Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need Azure DevOps CLI guidance to verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations. Uses an interactive install gate - if `az` or the Azure DevOps extension is missing, ask whether to show installation guidance before any work item commands. This should trigger for requests such as Azure DevOps work item list; List Azure Boards work item IDs; Azure DevOps WIQL query; Azure DevOps CLI planning workflow. Part of Plinth Toolkit

日本語の概要は準備中です。原文の説明を表示しています。

Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.

日本語の概要は準備中です。原文の説明を表示しています。

Assist with core product management activities including writing PRDs, analyzing features, synthesizing user research, planning roadmaps, and communicating product decisions. Use when you need help with PM documentation, analysis, or planning workflows that integrate with your codebase.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

日本語の概要は準備中です。原文の説明を表示しています。

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

日本語の概要は準備中です。原文の説明を表示しています。

Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

日本語の概要は準備中です。原文の説明を表示しています。

AiZynthFinder retrosynthetic route planning (CASP) from AstraZeneca Molecular AI. Monte Carlo tree search guided by a template-based neural expansion policy recursively disconnects a target SMILES until precursors are found in a purchasable stock. Covers config.yml (v4 format), aizynthcli batch screening, the AiZynthFinder/AiZynthExpander Python API, one-step disconnections, custom stocks via smiles2stock, scorers, Retro*/breadth-first/DFPN search alternatives, and reading output.json.gz / trees.json. Use for synthesis route planning, synthesizability screening, and building-block/precursor search. For reaction barriers use neb-irc-activation-energy; for 2D reaction scheme drawing use rdkit-chemdraw-cdxml.

日本語の概要は準備中です。原文の説明を表示しています。