一键在 Manus 中运行任何 Skill

task-planning

星标25

分支3

更新时间2026年6月16日 08:16

Reply with a structured plan instead of executing. Goal, assumptions, numbered steps, verification, risks. No file writes unless the user explicitly asks. Used when the user says "先列个计划" / "先想想再做".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Kkkirito-123

Kkkirito-123/ZLAgent

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

task-planning

Trigger

Use this skill when the user wants a plan rather than execution. Common phrases: "先列个计划", "不用马上做", "你先想清楚", "draft a plan", or explicitly "plan mode".

Do NOT use this when:

The task is a simple reminder / lookup → just do it.
The user only wants the answer, not the plan.
The user already has a plan and asks you to start executing.

Inputs

goal: what the user wants to end up with. If unclear, ask once.
constraints: time, tools allowed, files allowed to touch.
assumptions_known: anything the user already gave you.
output: default chat (reply in IM); only write a plan file when the user explicitly says "保存到 X" or "写进文档".

Steps

Restate the goal in one line. If unsure, ask one targeted question instead of guessing.
Surface the assumptions you are making. Mark unknowns clearly.
Break the work into bite-sized numbered steps. Each step must be:
- independently checkable
- small enough that a junior could do it
- paired with how you'd verify it (compile / test / smoke / manual)
List risks and rollback options for any step that touches state.
End with: "要我按这个计划执行吗？" — never start executing in the same turn.

Verification

The plan covers goal, assumptions, steps, verification, risks.
No step is "and then it's done" — every step has a check.
The reply is IM-friendly: numbered list, short lines, no walls.
The skill never proactively writes files unless output != chat.

Failure Signals

Plan reads like an essay.
Steps are vague ("research the problem", "make it work").
Verification missing on state-changing steps.
The agent silently executed instead of proposing the plan.

同仓库更多 Skills

同仓库

arxiv

Kkkirito-123/ZLAgent

Fetch and summarise recent papers from arxiv.org. Use this skill when the user wants a digest of today's or this week's cs.AI / cs.LG / cs.CL listings, a focused per-topic roundup, or a quick look at a specific submission.

2026-06-1625

code-review-quality

Kkkirito-123/ZLAgent

Lightweight code-review checklist the agent runs before declaring a patch ready. Catches the obvious classes of issue (dead code, missing error handling, weakened tests) without a full security audit. Adapted from addyosmani's "Review" lifecycle phase.

2026-06-1625

systematic-debugging

Kkkirito-123/ZLAgent

Root-cause-first debugging loop for code or runtime errors: understand the failure before proposing a fix. Adapted from Hermes' systematic- debugging — same iron law, smaller surface, ZLAgent-tool-aware.

2026-06-1625

verification-before-completion

Kkkirito-123/ZLAgent

Do not declare a task done without running verification. For code, that means running tests / smoke; for answers, that means checking the claim against a fresh source. Adapted from obra/superpowers and addyosmani's "Verify" lifecycle phase.

2026-06-1625

document-processing

Kkkirito-123/ZLAgent

Umbrella skill for user document workflows — PDF, Word, Excel, PowerPoint, text extraction, summarization. Dispatches to the right MCP / tool; proposes an install via mcp-discovery when no local capability fits. Adapted from Anthropic's docx/pdf/xlsx/pptx skills.

2026-06-1625

mcp-discovery

Kkkirito-123/ZLAgent

When the user wants something the agent doesn't have a tool for yet (travel planning, GitHub issues, Linear, weather, filesystem, ...), search the live MCP ecosystem for an existing server, propose installing it, and on confirm wire it up via mcp_manage. Adapted from Hermes' mcporter skill — same flow, ZLAgent-tool-aware.

2026-06-1625

name	task-planning
description	Reply with a structured plan instead of executing. Goal, assumptions, numbered steps, verification, risks. No file writes unless the user explicitly asks. Used when the user says "先列个计划" / "先想想再做".
version	0.1.0
tags	["productivity","planning"]
metadata	{"zlagent":{"category":"productivity","triggers":["列个计划","先想想","先想清楚","给我一个方案","不要直接动手","plan first","draft a plan","dont execute yet"],"capabilities":[],"related_skills":["systematic-debugging","skill-authoring"]}}

task-planning

Trigger

Use this skill when the user wants a plan rather than execution. Common phrases: "先列个计划", "不用马上做", "你先想清楚", "draft a plan", or explicitly "plan mode".

Do NOT use this when:

The task is a simple reminder / lookup → just do it.
The user only wants the answer, not the plan.
The user already has a plan and asks you to start executing.

Inputs

goal: what the user wants to end up with. If unclear, ask once.
constraints: time, tools allowed, files allowed to touch.
assumptions_known: anything the user already gave you.
output: default chat (reply in IM); only write a plan file when the user explicitly says "保存到 X" or "写进文档".

Steps

Restate the goal in one line. If unsure, ask one targeted question instead of guessing.
Surface the assumptions you are making. Mark unknowns clearly.
Break the work into bite-sized numbered steps. Each step must be:
- independently checkable
- small enough that a junior could do it
- paired with how you'd verify it (compile / test / smoke / manual)
List risks and rollback options for any step that touches state.
End with: "要我按这个计划执行吗？" — never start executing in the same turn.

Verification

The plan covers goal, assumptions, steps, verification, risks.
No step is "and then it's done" — every step has a check.
The reply is IM-friendly: numbered list, short lines, no walls.
The skill never proactively writes files unless output != chat.

Failure Signals

Plan reads like an essay.
Steps are vague ("research the problem", "make it work").
Verification missing on state-changing steps.
The agent silently executed instead of proposing the plan.