“plan”的搜索结果

Create an implementation plan for a feature — a dependency-ordered, actionable task list for the project. Has four modes: fast (a quick single-pass plan), full (a richer plan that can also create a git branch), ultra (a multi-file bundle — a manifest plus one deeply specified file per phase — for execution by a smaller model), and add (extend an existing plan with more tasks). Pick the mode from the user's wording: "full plan" runs full; "quick plan" or "fast plan" runs fast; "ultra plan", "ultraplan" or "ultra-plan" runs ultra; a plain "create a plan" with no qualifier defaults to fast; "add to the plan" or "extend the plan" runs add. Use whenever the user wants to plan a feature or task, e.g. "create a plan", "create a full plan", "create a quick plan", "run an ultra plan for the inventory system", "plan this feature", "add this to the plan", "extend the plan", "add a phase to the plan". Ultra runs only when the user names it — never because the feature looks large.

中文简介正在准备中。当前显示原文说明。

Turn a broad coding request into a concrete work plan grounded in the codebase. After user approval, it documents affected files, decisions, dependencies, and verification steps so a separate worker can carry out the implementation.

中文简介正在准备中。当前显示英语简介。

• Planning a large feature before coding
• Turning a vague request into defined tasks
• Preparing an implementation handoff

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 when a plan directory (plan.md + phase-*.md) needs a visual review. By DEFAULT this drives the STRUCTURED visual-plan artifact (visual-plan/plan.json) via the mewkit visual-plan CLI — generate if absent, validate, open the local studio (view/edit), and export plan.html from the approved artifact. Pass --static for the legacy prompt-only single-file plan.html template render. Triggers on "render this plan", "visualize the plan", "open the plan studio", "make a shareable plan page", "plan.html". This is the canonical owner of plan-as-visual-review. NOT for plan critique or scope review (see mk:plan-ceo-review / mk:validate-plan), NOT for generic code/diagram/diff visuals (see mk:preview), NOT for live media generation (see mk:multimodal).

中文简介正在准备中。当前显示原文说明。

口腔种植 (含 单牙/多牙缺失种植 / 全口 All-on-X / 即刻种植 即刻负重 / 上颌窦提升 / 牙槽嵴骨增量 GBR / 软组织移植 / 数字化种植 (CBCT 设计 + 口扫 + 导板 + CAD-CAM 上部) / 种植体周炎防治 / 种植修复 (基台 + 冠 + 杆卡 + 覆盖义齿) — 不含 普通牙体牙髓 / 正畸 / 儿牙 / 口腔颌面外科肿瘤 / 隐形矫治商业) (implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.) Master OS — automated mastery of implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business. problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「种植牙」「种植」「口腔种植」「牙种植」「implant」

中文简介正在准备中。当前显示原文说明。

Build a marketing plan matched to a company's budget, team, and stage. Organize acquisition, first use, retention, referrals, and revenue into a 90-day roadmap and 12-month outlook, with owners, metrics, and tools in Notion-ready Markdown.

中文简介正在准备中。当前显示英语简介。

• Build a marketing roadmap for founders or investors
• Turn audit findings into a prioritized action plan
• Combine scattered marketing work into one plan

ACTIVATES ONLY on an explicit user request for the ulw-plan workflow: the user themselves saying ulw-plan, ulw plan, /skill:ulw-plan, or asking in their own words for a work plan before coding. NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request, and the plan-gated reviewers (metis/momus) stay locked without a user request plus a written .omo/plans plan file. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode.

中文简介正在准备中。当前显示原文说明。

Archive completed plans. Moves finished folder plans from .unikit/code/plans/<folder>/ to .unikit/code/archive/plans/<folder>/, so plan lookup and the plan lists stop offering them; an unfinished plan moves only when the user picks it, and is marked as unfinished. Lists every plan with its created and last-change dates; plans can be picked by number or by date. Never deletes, renames or commits. Use when user says "archive plans", "archive completed", "archive old plans", "clean up plans", or "show archived plans". Not for .unikit/code/PLAN.md or FIX_PLAN.md; to check that a plan is really done use /unikit-verify, to commit the move use /unikit-commit.

中文简介正在准备中。当前显示原文说明。

Draft a GSD phase plan in Claude Code's ultraplan cloud while keeping your terminal free. Review and comment on the plan in a browser, then import it into your local workflow.

中文简介正在准备中。当前显示英语简介。

• Drafting a phase plan in the cloud
• Keeping the terminal free during planning
• Reviewing and commenting on a plan in a browser

Turn implementation plans, pull request changes, and technical concepts into HTML visual explanations with Plannotator styling. Present diagrams, mockups, and review priorities through an annotation interface, with approval controls for plans and proposals.

中文简介正在准备中。当前显示英语简介。

• Presenting an implementation plan for approval
• Explaining code changes and review priorities
• Illustrating system architecture and data flow

Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.

中文简介正在准备中。当前显示英语简介。

• Reviewing and approving plans or specifications
• Reviewing local code changes or pull requests
• Annotating documents or running local apps

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

中文简介正在准备中。当前显示原文说明。

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで役割を分けて進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」「0 節の Issue を順に片付けて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

中文简介正在准备中。当前显示原文说明。

Issue または ExecPlan を、人の確認を待たずに「準備 → 実装 → 範囲の照合 → 検証 → 自己レビュー → push → PR」まで進めるスキル。`/run-issue <番号>`・`/run-plan <ExecPlan のパス>`・`/finish-task` を提供する。ユーザーが「/run-issue」「/run-plan」「Issue を自走で直して」「ExecPlan を最後まで進めて」と依頼したときに使う。ExecPlan を作るだけなら exec-plan、次のタスクを選ぶだけなら roadmap-manager を使う。

中文简介正在准备中。当前显示原文说明。

Have agents with different roles challenge a proposed approach, exposing weak assumptions, missed interactions, and unnecessary complexity. Surviving findings go to a dedicated planning agent, which produces sequenced tasks with explicit success criteria.

中文简介正在准备中。当前显示英语简介。

• Checking assumptions before committing to a plan
• Finding integration risks and overlooked edge cases
• Challenging unnecessary complexity in a design

Create an implementation plan grounded in code relationships and verified source files, with proposed changes, test scenarios, risks, and a structured handoff for an implementation agent. It can also revisit and strengthen an existing plan.

中文简介正在准备中。当前显示英语简介。

• Planning a new feature
• Assessing a shared API change before implementation
• Strengthening and rechecking an existing plan

Develop an implementation plan through sequential Planner, Architect, and Critic reviews. Compare options, document risks and acceptance checks, and preserve the plan and review records for a later handoff to `$ultragoal`.

中文简介正在准备中。当前显示英语简介。

• Compare approaches before implementation
• Plan testing and failure scenarios for high-risk changes
• Review a plan without starting implementation

Keep plans, research findings, and progress in Markdown files for complex agent work. Separate task plans and automatic planning reminders help the agent recover saved context, track decisions, and identify the next action.

中文简介正在准备中。当前显示英语简介。

• Resuming long research tasks
• Tracking phases and the next action
• Separating plans for concurrent tasks

Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.

中文简介正在准备中。当前显示英语简介。

• Finding recurring reasons for plan rejection
• Understanding how review expectations changed
• Deriving planning instructions from past feedback

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

中文简介正在准备中。当前显示原文说明。

Enhance an existing marketing plan with parallel research. Use when the agent has a draft plan (brand strategy, campaign brief, content calendar, launch plan) that needs strengthening with real data. Triggers on 'deepen this plan', 'strengthen this strategy', 'research gaps in my plan', 'make this plan better', 'this plan is too surface level', 'add research to this', 'validate this plan', 'back this up with data', or when a plan exists but lacks audience data, competitive positioning, or keyword strategy. Make sure to use this whenever someone has an EXISTING plan that feels thin or unresearched — even if they just say 'is this plan good enough?' or 'what's missing here?', they likely need deepening. This skill ENHANCES existing plans — it does not create new ones. If no plan exists, route to /brainstorm or /launch-strategy first.

中文简介正在准备中。当前显示原文说明。

Plan and configure GKE cluster networks, including private nodes, IP address ranges, DNS, and outbound connectivity. Use the guidance to set up VPC-native networking and Dataplane V2, which provides built-in network policy enforcement.

中文简介正在准备中。当前显示英语简介。

• Designing a private GKE cluster network
• Planning IP ranges for Pods, Services, and nodes
• Configuring outbound access with a static source IP

Creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements upfront, then generates a visual HTML plan document for your review and approval. **plan-alm does not deploy anything itself** — it is a planner. After you approve the plan, run the individual ALM skills (setup-solution, setup-pipeline, deploy-pipeline, or export-solution/import-solution); each detects the approved plan and executes the right step in order, keeping the plan updated as it runs. Use when asked to: "plan my alm", "set up alm", "create deployment plan", "plan my deployments", "help me deploy to multiple environments", "set up promotion strategy", "create cicd plan", "plan site promotion", "help me go to production", "set up pipeline for my site".

中文简介正在准备中。当前显示原文说明。

This skill should be used when the user asks to "dev-webtest-plan", "Webテスト計画を生成", "テスト計画を作成", "webtest plan", "E2Eテスト計画", "画面テスト計画", "generate webtest plan", "create test plan from requirements", "webtest計画を更新", "テスト計画の差分更新", "update webtest plan", "画面仕様からテスト更新". dev-planの出力からPlaywright用のWebテスト計画ファイルを自動生成する。画面仕様の変更差分からテスト計画を更新する差分更新モードも対応。

中文简介正在准备中。当前显示原文说明。