Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

memory-plan-execution

Estrelas17

Forks11

Atualizado15 de junho de 2026 às 18:59

Save the approved plan and checkpoint when execution starts, and verify all plan checkbox items are complete before claiming the task is finished

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

3vilM33pl3

3vilM33pl3/memory

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	memory-plan-execution
version	0.9.5
description	Save the approved plan and checkpoint when execution starts, and verify all plan checkbox items are complete before claiming the task is finished

Memory Plan Execution Skill

Use this skill when:

a planning session has ended and the user approved execution
plan-backed work is underway and the agent needs to verify completion
the approved plan changed materially and needs to be resaved for the same thread

Do not use this skill for:

general project questions
interruption recovery without a plan transition
post-task remembering once the work is already verified complete

Scripts

Save the approved plan and checkpoint together:

go run ./.agents/skills/memory-layer/scripts/main.go start-plan-execution \
  --project <project-slug> \
  --plan-file /tmp/approved-plan.md

Verify the approved plan is fully executed:

go run ./.agents/skills/memory-layer/scripts/main.go finish-plan-execution \
  --project <project-slug>

Optional explicit checkpoint-only helper:

go run ./.agents/skills/memory-layer/scripts/main.go checkpoint-project \
  --project <project-slug> \
  --note "Plan approved; starting implementation"

Workflow

When the user approves a real plan, run start-plan-execution before implementation starts.
The approved plan must contain Markdown checkbox items so completion can be verified later.
If the plan changes materially during execution, save the revised approved plan first with the same thread key.
Before claiming plan-backed work is finished, run finish-plan-execution.
Do not present the task as finished if any checkbox item remains unchecked.
If there is no approved plan and the user gives a direct actionable task, use the umbrella skill's start-task-execution workflow instead of this plan workflow.

Model Routing

Keep this skill on the stronger engineering path.

Runtime Requirement

This focused skill uses the shared Go helper under .agents/skills/memory-layer/scripts/. go must be available on PATH for these helper commands to run.

Mais deste repositório

mesmo repositório

memory-layer

3vilM33pl3/memory

Umbrella entrypoint for Memory Layer workflows; use for broad memory-related turns, shared invariants, and docs/admin work, while focused query/resume, plan-execution, and remember skills handle the narrow workflows

2026-06-2717

memory-direct-task-start

3vilM33pl3/memory

Record a task memory before starting direct no-plan implementation work when the user asks to implement, fix, change, add, update, release, install, or otherwise mutate the repository without first approving a plan

2026-06-1517

memory-github-init

3vilM33pl3/memory

Guide first-time GitHub repository initialization for a Memory Layer project; use when setting up or auditing GitHub remotes, repository metadata, Actions workflows, secrets, variables, branch protection, required checks, or Memory Layer repo onboarding, with discovery and dry-run review before write-capable changes

2026-06-1517

memory-project-init

3vilM33pl3/memory

Initialise or refresh Memory Layer in a project directory after Memory Layer is already installed; use for repo-local setup with .mem, .agents/memory-layer.toml, and repo-local memory skills, previewing writes before applying them

2026-06-1517

memory-query-resume

3vilM33pl3/memory

Query curated project memory before answering repo-specific questions, and use resume to get back into flow after interruptions

2026-06-1517

memory-remember

3vilM33pl3/memory

Remember meaningful completed work by capturing task context and curating it into durable project memory with provenance

2026-06-1517

Memory Plan Execution Skill

Use this skill when:

a planning session has ended and the user approved execution

plan-backed work is underway and the agent needs to verify completion

the approved plan changed materially and needs to be resaved for the same thread

Do not use this skill for:

general project questions

interruption recovery without a plan transition

post-task remembering once the work is already verified complete

Scripts

Save the approved plan and checkpoint together:

go run ./.agents/skills/memory-layer/scripts/main.go start-plan-execution \ --project <project-slug> \ --plan-file /tmp/approved-plan.md

Verify the approved plan is fully executed:

go run ./.agents/skills/memory-layer/scripts/main.go finish-plan-execution \ --project <project-slug>

Optional explicit checkpoint-only helper:

go run ./.agents/skills/memory-layer/scripts/main.go checkpoint-project \ --project <project-slug> \ --note "Plan approved; starting implementation"

Workflow

When the user approves a real plan, run start-plan-execution before implementation starts.

The approved plan must contain Markdown checkbox items so completion can be verified later.

If the plan changes materially during execution, save the revised approved plan first with the same thread key.

Before claiming plan-backed work is finished, run finish-plan-execution.

Do not present the task as finished if any checkbox item remains unchecked.

If there is no approved plan and the user gives a direct actionable task, use the umbrella skill's start-task-execution workflow instead of this plan workflow.

Model Routing

Keep this skill on the stronger engineering path.

Runtime Requirement

This focused skill uses the shared Go helper under .agents/skills/memory-layer/scripts/. go must be available on PATH for these helper commands to run.