PlanSuite

Create, finalize, and execute file-based project plans with subplans, using checkpoints and logs for controlled, session-based implementation and progress tr...

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 1.9k · 5 current installs · 5 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
There is no separate description in registry metadata, but the SKILL.md clearly defines a file-based planning/execution workflow (task_plan.md, progress.md, findings.md). The resources it requires (none) and actions it prescribes (create/update local files) are consistent with a planning tool. Minor note: source/homepage are unknown and the top-level registry description is missing, which reduces provenance but does not make the behavior incoherent.
Instruction Scope
Instructions are tightly scoped to creating and updating three files in the current working directory, enforcing a freeze/execute workflow, and recommending use of an isolated session (sessions_spawn) for execution. There are no instructions to read unrelated system files, access external endpoints, or exfiltrate data. The guidance to 'do not paste these three files into chat' simply enforces file-based persistence.
Install Mechanism
No install spec and no code files — this is instruction-only, so nothing will be downloaded or written by an installer. Lowest risk per install mechanism.
Credentials
No environment variables, credentials, or config paths are requested. The instructions only require permission to create/update files in the current working directory, which is proportional to a file-based planning workflow.
Persistence & Privilege
The skill does not request 'always: true' or other elevated persistence. It only instructs the agent to write three files in the working directory and to spawn an isolated session for execution — this is normal for a project-run workflow and does not modify other skills or global agent configuration.
Assessment
This skill is a local, file-based planning workflow and appears coherent: it creates/updates task_plan.md, progress.md, and findings.md in whichever working directory the agent runs in. Before installing or invoking it: (1) understand the agent will write to your current working directory — back up or run in an empty/sandbox directory if you care about file safety; (2) avoid putting secrets or sensitive credentials into the plan files; (3) note the registry metadata lacks a homepage/description and the source is unknown — if provenance matters to you, prefer skills with clear authorship; (4) check whether your agent platform’s sessions_spawn (isolated session) capability is available and behaves as you expect. Other than those operational cautions, the skill's requests and instructions are proportionate to its stated planning purpose.

Like a lobster shell, security has layers — review code before you run it.

Current versionv0.1.3
Download zip
latestvk973e2sjmdf9wqty8mq5sagnpn80jn2g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

PlanSuite

把“写计划(含子计划)→ 冻结计划(变更控制)→ 独立会话执行(带检查点)”合成一个最小可用流程。

文件结构(在当前工作目录创建/维护)

  • task_plan.md:计划主文件(含子计划/里程碑)
  • progress.md:执行进度(每次推进都要写)
  • findings.md:发现/决策/坑点(避免重复踩坑)

不要把这三份写到聊天里:写到文件,才能恢复/续跑。

工作流(强约束,防跑偏)

0) 初始化(第一次做这个项目)

  1. 如果缺文件:用模板创建 task_plan.md/progress.md/findings.md(见 templates/)。
  2. 让用户确认目标、范围、约束、完成定义(DoD)。

1) 计划阶段(拆子计划)

task_plan.md 里输出:

  • 背景/目标
  • 范围(做/不做)
  • 风险 & 回滚
  • 子计划(Milestones):每个子计划要有
    • 输入/输出
    • 验收标准
    • 预计工具调用/文件改动
    • 风险与回滚点

2) 冻结阶段(FINALIZED)

只有当用户明确说“按这个计划执行”后:

  1. task_plan.md 顶部写入:STATUS: FINALIZED + 时间戳。
  2. 把“接下来要执行的子计划编号/名称”写入 progress.mdNext

规则:未 FINALIZED 不允许进入执行阶段(最多做调查/补充计划)。

3) 执行阶段(独立会话 + 检查点)

当进入执行:

  1. 建议用 sessions_spawn 开一个隔离执行会话(避免污染主会话上下文)。
  2. 每完成一个子计划:
    • 更新 progress.md(Done/Next/Blockers)
    • 更新 findings.md(关键决策、踩坑、验证命令、回滚步骤)
  3. 检查点策略(默认每个子计划至少一次):
    • 执行前:复述子计划的 DoD + 风险 + 回滚
    • 执行后:给出验证步骤 + 结果

4) 变更控制(计划变更)

如果执行中发现计划不成立:

  1. 不要“边做边改”。先写入 findings.md,再把变更提案写入 task_plan.md
  2. STATUS 改为 DRAFT,等待用户重新确认。

你在什么时候用什么文件

  • 需要问清楚/拆任务 → task_plan.md
  • 需要告诉用户进度/下一步 → progress.md
  • 需要记录结论/命令/坑/回滚 → findings.md

模板

  • templates/task_plan.md
  • templates/progress.md
  • templates/findings.md

Files

5 total
Select a file
Select a file to preview.

Comments

Loading comments…