'plan' 검색 결과

Turn observations or preliminary findings into testable research plans. The skill separates candidate hypotheses from evidence, develops competing explanations and distinguishing predictions, and helps specify measurements and analysis plans for preregistration, a research plan recorded before testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an observation into testable research hypotheses
• Compare competing explanations and distinguishing predictions
• Define measurements and review an analysis plan

Structure a post-acquisition improvement plan linking revenue, cost, and operational initiatives to EBITDA, a profit measure. Produce a roadmap with 100-day priorities, performance targets, responsible owners, and an Excel model showing each initiative’s profit contribution.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the first 100 days after an acquisition
• Mapping growth and cost initiatives to profit targets
• Preparing a value creation roadmap for the board

Turn feature requests, refactoring work, package upgrades, or infrastructure changes into structured Markdown implementation plans. Each plan defines concrete tasks, dependencies, affected files, and validation criteria for execution by AI agents or people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan the implementation of a new feature
• Break refactoring work into concrete tasks
• Prepare a package upgrade plan

Turns vague development requests into reviewed plans through planning, architecture, and quality-review agents. It compares alternatives, defines testable acceptance criteria, and records decisions, stopping before implementation unless execution has been explicitly approved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining the scope of a vague development request
• Comparing implementation approaches before coding
• Planning migrations or security-sensitive changes

Explains how to replace the removed $pipeline command with $plan for planning and $team for coordinated parallel work. This retirement notice provides migration guidance rather than an executable workflow of its own.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating instructions that still reference $pipeline
• Choosing separate commands for planning and parallel execution
• Finding the command for persistent goal runs

Turn a project idea into a detailed system plan before coding. Organize architecture, data flows, dependencies, and file-level tasks in a linked Markdown workspace, with research references, consistency checks, and saved state for resuming later.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a new system before writing code
• Break implementation into tasks with files and dependencies
• Check a design for gaps and contradictions

Organize multi-step agent tasks with persistent Markdown files for plans, findings, and progress. Records decisions, errors, and test results, then reloads the selected task's planning files to resume work after an interruption.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning research that involves many tool calls
• Resuming work after an interruption
• Recording errors and test results

Check the `.planning/` directory for missing files, invalid settings, inconsistent state, and orphaned plans. Report issues to address, optionally request repairs, or check context usage—the share of the session’s text capacity already used.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking planning files for missing content or inconsistencies
• Finding orphaned plans
• Requesting repairs after a planning directory check

Build and update a study plan for bar exams or law school courses. Allocate time around weak subjects, available hours, and rest days, then adjust upcoming sessions using recorded practice results and progress.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a long-term bar exam study plan
• Planning for law school finals
• Rebalancing study time using practice results

Review Markdown files, HTML files, URLs, or folders in Plannotator’s annotation interface. The agent responds to requested changes and distinguishes them from approvals, optional approval notes, and sessions closed without feedback.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a Markdown document
• Collecting comments on HTML or web pages
• Opening a folder for annotation

Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code changes from Kiro
• Review a separate working directory
• Open a review for a pull request URL

Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

Carry out approved technical plans in phases, checking success criteria and recording progress as work proceeds. Larger plans can use separate agents with saved handoff notes, while manual verification keeps users involved at phase boundaries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an approved technical plan
• Checking results at each implementation phase
• Resuming work from unfinished plan items

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan future work, investigate before building, research a topic, or compare the alternatives for a choice. Takes optional free text. The skill reads the request, open drafts, accepted canon, branch, and code, then creates only the documents a later reader needs — none for a small fix. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'plan the onboarding journey', 'investigate X before we plan', 'compare the alternatives for Y', 'REST or a queue? two teams disagree', 'I need market research before we plan', 'we are regulated — trace the requirements'. With no arguments it resumes an open planning draft or offers what to plan next. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Specify plant models for closed-loop simulation: system specs, architecture, build plans, validation plans. Use when creating, updating, or reviewing plant model specifications, planning plant model architecture, or planning plant model validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan a complete affiliate funnel from research to revenue. Triggers on: "plan my affiliate funnel", "create a funnel strategy", "affiliate business plan", "how to start affiliate marketing", "full funnel roadmap", "plan from scratch", "week by week affiliate plan", "chain skills together", "build my funnel", "affiliate marketing roadmap", "step by step affiliate plan", "onboarding plan".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the next period content plan must be built from last period DATA — keep and replicate winners, cut losers, at most two new hypotheses, a 70/20/10 mix, a four-week overview, and an owner per slot. Trigger on 'next content plan', 'content plan for next month', 'plan from the audit', 'what should we post next quarter', 'scale what worked', 'plan content using the numbers'. Also use when a report just landed and the user asks what to do with it. Not for — auditing the past period first, see `39-content-audit-global`; turning the plan into a dated calendar, see `01-content-calendar-global`; the next period ADS plan, see `57-next-ads-plan-global`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a PAID MEDIA plan is needed — work backward from revenue to max CPA and required budget, split spend across channels, funnel stages, and campaign types, build a ramp-up timeline, set KPI targets per channel, and prepare a contingency plan. Trigger on 'media plan', 'paid media budget', 'how much should I spend on ads', 'channel mix for the campaign', 'plan the ad budget', 'we have 10k a month and no plan'. Also use when a budget number exists and nobody has decided where it goes. Not for — the pure revenue-to-budget math, see `10-reverse-kpi-global`; the whole marketing budget including non-paid, see `61-budget-planning-global`; the next period plan built from results, see `57-next-ads-plan-global`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating or refining a structured Java implementation plan from trusted issue summaries, approved designs, ADRs, OpenSpec changes, existing plans, or a valid combination. The plan records its source artifacts and derivation direction and can remain the execution artifact without requiring OpenSpec. This should trigger for requests such as Create a plan from an issue; Create a plan from OpenSpec; Design an implementation plan; Refine an existing plan. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze task complexity and route to a mode by artifact: direct fix for clear-scope changes, or a plan file when the approach needs to be written down. Use when the user asks to "turboplan", "run turboplan", "plan this task", "turbo plan mode", "plan and implement", or "use turboplan instead of plan mode".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce an implementation plan at .turbo/plans/<slug>.md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", or needs a first-draft plan file before refinement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ARK 套餐管理(Agent Plan / Coding Plan,个人版 + 企业版):查询持有 / 购买 / 续费 / 模型清单 / 轮换 APIKey,**以及企业版席位的全部管理操作**:列出席位(`plans team seat-list`)、给员工分配席位(`plans team seat-assign`)、查谁绑了哪个 seat、轮换席位 APIKey(`plans team rotate-apikey`)。也负责购买参数的逐步澄清，以及 `payment_failed` + Order ID 后回到已有订单补单/取消，禁止重新 buy。命中关键词:套餐 / 买 / 续费 / 列席位 / 看 seat 绑定 / 谁绑了哪个 seat / 给员工分席位 / 解绑 / 团队席位 admin 视图 / 轮换 APIKey。反触发：Token 额度包/资源包不是 Agent Plan/Coding Plan，应走 arkcli-profile 判断 platform 切面。**用量类问题(还剩多少额度 / 用了几成 / 每个 seat 用了多少)走 [arkcli-usage](../arkcli-usage/SKILL.md)。**动词路由:**列 / 绑 / 分 / 轮换 / 解绑** → 这里;**用 / 消耗 / 多少** → arkcli-usage。另含 harness-status:只读查看本机 AI Agent(claude-code/codex/opencode/openclaw/trae)上 Agent Plan 内置 MCP(豆包搜索/dataPro/OpenViking)装没装、key 就没就绪;命中:我的 MCP 装好了吗 / 查 MCP 安装状态 / 看 agent 上的 MCP / harness 状态。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan garden activities using solar, lunar, and biodynamic calendars. Covers USDA hardiness zones, frost date calculation, equinox/solstice anchoring, synodic lunar cycle (waxing/waning), ascending/descending moon, Maria Thun biodynamic calendar (root/leaf/flower/fruit days), succession planting schedules, and seasonal task planning. Use when planning a new growing season and needing a planting schedule, integrating lunar or biodynamic timing into garden practice, calculating frost dates and planting windows for a specific zone, setting up succession planting for continuous harvest, or conducting end-of-season review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.