「plan」の検索結果

Agent assignment guidance, architecture patterns, and dependency ordering for fullstack-typescript plans.

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

Templates and guidance for implementation plans with dynamic phase generation.

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

Phase 2 of 5 — collaborative system design plus change-footprint mapping; outputs an ARCH doc for generate-tasks. Use only when the user asks to run Phase 2, plan the architecture, or design the solution — never trigger automatically from a design question.

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

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

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

Execute detailed plans in batches with review checkpoints

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

Observe and assess a garden using a structured sensory protocol adapted from Coordinate Remote Viewing. Covers pre-entry clearing (meditate checkpoint), Stage I gestalt impression, Stage II sensory layer (leaf, stem, root, soil), Stage III pattern recognition with AOL management, and garden health triage matrix (heal checkpoint). Use before any intervention, when plants show stress symptoms, at seasonal transitions, when evaluating a new garden site, during regular health monitoring, or after extreme weather events such as frost or heat waves.

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

Prepare herbal remedies from Hildegard von Bingen's Physica. Covers plant identification, preparation methods (tinctures, poultices, infusions, decoctions), dosage guidance, contraindications, and safety review based on 12th-century medieval pharmacopeia. Use when needing an herbal remedy for a specific ailment using Hildegardian pharmacopeia, seeking guidance on preparation methods and dosage, researching medieval herbal medicine, or integrating Hildegard's plant wisdom into holistic health practice.

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

Forecast infrastructure and application metrics using Prophet or statsmodels for capacity planning, cost optimization, and proactive scaling. Visualize predictions in Grafana and set up alerts for projected resource exhaustion. Use when forecasting infrastructure capacity needs for CPU, memory, or disk, planning hardware procurement for next quarter, predicting cost trends to optimize cloud spending, or setting up proactive scaling policies based on predicted load.

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

Identify insects using body plan analysis, dichotomous keys to order, wing venation, mouthpart type, antennae form, leg and tarsal structure, and confidence levels. Covers the fundamental hexapod body plan verification, a simplified dichotomous key to major orders, wing venation and type analysis, mouthpart classification, antennae morphology, leg specialization and tarsal formula, and a structured confidence assessment framework. Use when you need to identify an unknown insect beyond preliminary order placement, are working through a specimen for taxonomic study, want to distinguish between similar orders or families, or need to assign a confidence level to a field identification.

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

Draft a project charter that defines scope, stakeholders, success criteria, and initial risk register. Covers problem statement, RACI matrix, milestone planning, and scope boundaries for both agile and classic methodologies. Use when kicking off a new project or initiative, formalizing scope after an informal start, aligning stakeholders before detailed planning begins, or transitioning from discovery to active project work.

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

Analyze an arbitrary codebase to auto-detect workflows, data pipelines, and file dependencies using putior's put_auto() engine. Produces an annotation plan that maps detected I/O patterns to source files across 30+ supported languages with 902 auto-detection patterns. Use when onboarding onto an unfamiliar codebase to understand data flow, starting putior integration in a project without existing annotations, auditing a project's data pipeline before documentation, or preparing an annotation plan before running annotate-source-files.

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

Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.

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

Analyze the dynamics of diffusion processes using stochastic differential equations, Fokker-Planck equations, first-passage time distributions, and parameter sensitivity analysis. Use when deriving probability density evolution for a continuous-time diffusion process, computing mean first-passage times for bounded diffusion, analyzing how drift and diffusion parameters affect process behavior, or validating closed-form solutions against stochastic simulation.

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

Rates responses and plans against quality rubrics. Used for plan validation, response quality audits, and multi-agent consensus.

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

Agent Brain /brain-plan: the brief/design is strong enough to implement.

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

Trains the HUMAN user's critical thinking through four modes: drill (argument-analysis items with a single defensible answer, judge stance), scene (Socratic exploration of synthetic scenes or user-supplied material, no verdicts on interpretations; includes a configure track — design the information request and verification plan for a decision before any analysis), expedition (guided audit of impossible-tier problems from verified packs), and detective (a runtime-generated multi-layer case worked as an escape room, guide-and-judge stance). Use when the user wants to practice critical thinking, analyze arguments, hunt assumptions, examine bias, train reasoning, or decide what information a decision needs first. Triggers: critical thinking practice, train my thinking, drill, scene, byom, configure, information plan, what would I need to know, spot manipulation tactics, scam literacy, 批判思考練習, 話術辨識, detective, 查案, 破案, 偵探.

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

Investigate datasets and resolve entities using OpenPlanter methodology — cross-reference heterogeneous sources, build Admiralty/ACH confidence-tiered evidence chains, and apply OSINT tradecraft. Triggers on entity resolution, cross-reference datasets, evidence chain, OSINT investigation, structured investigation.

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

Plan the UX and UI for a feature before writing code. Run a structured discovery interview, then produce a design brief (.design-context.md) that guides implementation. Establishes design direction, constraints, and strategy before any code is written. Triggers on plan the design, design brief, shape the UX, before we build, design discovery.

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

Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.

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

Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).

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

機能要件から画面構成・ワイヤーフレームまでを段階的に落とし込むスキル。 design-discussion や feature-discussion の成果物を入力として、 2ステップ（アクションフロー → ワイヤーフレーム + 画面設計ノート）で画面設計を行う。 ワイヤーフレームを見ながらユーザーと一緒に必要な機能・画面要素を詰めていく。 成果物は PlantUML Salt による視覚的なワイヤーフレーム。 Use when: 機能から画面に落としたい、画面構成を考えたい、 ワイヤーフレームを作りたい、画面設計をしたい、画面フローを整理したい。 design-discussion の後に使うと効果的。 Triggers: "画面構成", "画面設計", "ワイヤーフレーム", "画面に落とす", "ui flow design", "UIフロー設計", "wireframe", "画面を考えたい", "UIフロー", "画面遷移", "screen design", "画面フロー", "screen flow"

エージェントを長時間稼働させて大きな実装タスクを完遂するためのスキル。 TODO ファイル (.md) を管理しながら、高レベル TODO → 細かい TODO に分解 → 実装 → サブエージェントによるレビュー → 不足分の TODO 追加 のサイクルを回す。 コンテキストが大きくなっても TODO ファイルが状態の真実の源泉として機能するため、 長時間・大規模な変更でも迷子にならずに着実に完遂できる。 team-plan や team-implement とは異なり、1人のメインエージェントが逐次的に実装し、 各段階をレビューエージェントが品質検証する。 Use when: 大きな実装タスクを段階的に進めたい、エージェントに長時間任せたい、 実装中に TODO を追加しながら進めたい、各ステップの品質をサブエージェントにレビューさせたい、 長時間の実装を構造化したい、放置しても安心して任せられる実装フローが欲しい。 Triggers: "long-run", "段階的に実装", "TODO駆動で実装", "大きな実装", "ステップバイステップで実装", "レビューしながら実装", "long run implement", "実装を進めて", "大規模実装", "iterative implement", "長時間実装", "エージェントに任せて", "放置で実装"

仕様駆動設計。仕様書からクラス責務を分析し、純粋関数を特定、テストファーストで単体テストを設計する。既存Planに追記。

Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.

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