「planning」の検索結果

Route planning for Berlin public transport (BVG)

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

Expert-level construction management covering project planning, scheduling, cost estimation, procurement, quality control, safety, and contract administration.

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

Expert-level organic chemistry knowledge. Use when working with organic reactions, mechanisms, functional groups, stereochemistry, synthesis planning, spectroscopy, or named reactions. Also use when the user mentions 'organic reaction', 'mechanism', 'functional group', 'stereochemistry', 'synthesis', 'NMR', 'IR spectroscopy', 'SN1', 'SN2', 'elimination', 'addition', 'aromatic', 'carbonyl', or 'named reaction'.

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

Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.

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

Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.

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

Create and commit a durable handoff document that gives a fresh agent the context and prompt to continue the current planning or implementation work. Use only when explicitly invoked as `$handoff` or when the user explicitly requests a handoff.

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

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

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

Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.

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

Execute the implementation planning workflow using the plan template to generate design artifacts.

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

Execute the implementation planning workflow using the plan template to generate design artifacts.

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

Marketing operations manager handling budget planning, financial reporting, meeting preparation and follow-up, vendor management, and administrative workflows for marketing and communications departments. Designed for SME leaders who need to minimize time spent on operational overhead.

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

Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.

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

Use BEFORE planning/coding against a DB schema, API/GraphQL shape, DTO/Model/Entity, or vendor package — read the real source, emit an Evidence Report, stop inventing fields.

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

Refine a Jira/Linear ticket before planning — 'refine ticket', 'tighten AC on PROJ-123', 'ist das Ticket klar?'; rewritten ticket, risks, persona voices, close-prompt.

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

Use when picking a mobile E2E framework — Detox / Appium / Maestro / XCUITest / Espresso — or planning iOS Simulator / Android Emulator coverage in CI for RN, Expo, or native apps.

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

Frontend design heuristics and the loop applying them: existing-ui-audit, brief, inventory, build, review. Use when building or changing any UI, not only when planning one.

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

Use when the user says "plan a feature", "brainstorm", "explore this idea", or wants to go from idea to structured plan and roadmap.

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

Use when staging multi-component or uncertain work — tackle the load-bearing unknown first (risk-first decomposition), not the easy parts first.

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

Use when designing APIs, planning endpoints, REST conventions, versioning, or deprecation — even when the user just says 'expose this as an endpoint' without naming API design.

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

Crie e gerencie arquivos de planejamento markdown persistentes para execução estruturada de tarefas. Use quando o usuário pedir para "criar um plano", "acompanhar progresso", "iniciar um projeto de pesquisa", ou quando uma tarefa exigir mais de 5 chamadas de ferramenta e precisar de rastreamento de fases estruturado para manter o foco e evitar desvio de objetivo.

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

Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.

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

[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.

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

[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.

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

[Planning] Use when you need to validate a plan with critical questions interview.

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