planning-with-files

Manus-style file-based planning for complex tasks. Use task_plan.md, findings.md, and progress.md to maintain persistent context. Use for multi-step tasks, research, or work spanning many tool calls.

Ir para a instalação

Repositório: oimiragieo/agent-studio
Última atividade na origem: 21 de abril de 2026 às 23:45
Idioma detectado do SKILL.md: inglês
Estrelas: 36
Forks: 6

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

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ê.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/oimiragieo/agent-studio --skill planning-with-files

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

10 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

agent-enhancement-worker

Agent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field

2026-07-02

context-worker

Context management — pre-compact persistence, threshold alignment, microcompact/circuit breaker detection

2026-07-02

hook-routing-worker

Hook enhancements — updatedInput for bash safety prefixes, suppressOutput for verbose blocks, denial-based routing feedback

2026-07-02

Ver todas deste repositório

name	planning-with-files
description	Manus-style file-based planning for complex tasks. Use task_plan.md, findings.md, and progress.md to maintain persistent context. Use for multi-step tasks, research, or work spanning many tool calls.
version	1.1.0
tools	["Read","Write","Edit","TaskUpdate","TaskList"]
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	cf607bcd4c0a461c

Planning with Files - Manus-Style File-Based Planning

Work like Manus (the $2B AI agent Meta acquired): Use persistent markdown files as your "working memory on disk."

Core Principle

Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)

→ Anything important gets written to disk.

The 3-File Pattern

For every complex task, create THREE files in your project directory:

task_plan.md      → Track phases and progress
findings.md       → Store research and findings
progress.md       → Session log and test results

Templates are available at: .claude/templates/planning/

When to Use This Pattern

Use for:

Multi-step tasks (3+ steps)
Research tasks
Building/creating projects
Tasks spanning many tool calls
Anything requiring organization

Skip for:

Simple questions
Single-file edits
Quick lookups

Critical Timing Rules

These rules simulate hooks to ensure proper workflow:

📌 At Task Start (SessionStart)

MUST create all three files FIRST before any other work:

Create task_plan.md using the template
Create findings.md using the template
Create progress.md using the template
Fill in the Goal section in task_plan.md

Why: Without planning files, you'll forget goals after 50+ tool calls.

📌 Before Major Decisions (PreToolUse)

MUST re-read task_plan.md before:

Writing or editing files
Executing commands
Making architectural decisions
Implementing features

How: Use the Read tool to refresh the plan in your context.

Why: This keeps goals fresh in your attention window (Manus's "attention manipulation").

📌 After File Operations (PostToolUse)

MUST update status immediately after:

Writing files
Editing files
Completing a task phase

How: Edit task_plan.md to update phase status:

File	Purpose	When to Update
`task_plan.md`	Phases, progress, decisions	After each phase
`findings.md`	Research, discoveries	After ANY discovery
`progress.md`	Session log, test results	Throughout session

Situation	Action	Reason
Just wrote a file	DON'T read	Content still in context
Viewed image/PDF	Write findings NOW	Multimodal → text before lost
Browser returned data	Write to file	Screenshots don't persist
Starting new phase	Read plan/findings	Re-orient if context stale
Error occurred	Read relevant file	Need current state to fix
Resuming after gap	Read all planning files	Recover state

Question	Answer Source
Where am I?	Current phase in task_plan.md
Where am I going?	Remaining phases
What's the goal?	Goal statement in plan
What have I learned?	findings.md
What have I done?	progress.md

Anti-Pattern	Why It Fails	Correct Approach
Using session task tools for persistence	In-memory task tracking is volatile; lost on context reset	Create `task_plan.md` file on disk — survives resets
Stating goals once and forgetting them	Context fills; goals drift without anchoring	Re-read plan file before every major decision
Hiding errors and retrying silently	Silent retries repeat the same failure endlessly	Log every error to plan file with attempt count
Stuffing all research into context	Context window fills; earlier content gets lost	Store large content and discoveries in `findings.md`
Starting execution without a plan	Undefined scope leads to wasted work and missed steps	Create all three planning files FIRST before any action

Principle	Implementation
Filesystem as memory	Store in files, not context
Attention manipulation	Re-read plan before decisions
Error persistence	Log failures in plan file
Goal tracking	Checkboxes show progress
Completion verification	Check all phases before stopping

planning-with-files

Opções de instalação

Revise os arquivos de origem

Planning with Files - Manus-Style File-Based Planning

Core Principle

The 3-File Pattern

When to Use This Pattern

Critical Timing Rules

📌 At Task Start (SessionStart)

📌 Before Major Decisions (PreToolUse)

📌 After File Operations (PostToolUse)

Planning with Files - Manus-Style File-Based Planning

Core Principle

The 3-File Pattern

When to Use This Pattern

Critical Timing Rules

📌 At Task Start (SessionStart)

📌 Before Major Decisions (PreToolUse)

📌 After File Operations (PostToolUse)

📌 Before Task End (Stop)

The 6 Critical Rules

1. Create Plan First

2. The 2-Action Rule

3. Read Before Decide

4. Update After Act

5. Log ALL Errors

6. Never Repeat Failures

The 3-Strike Error Protocol

File Purposes

Read vs Write Decision Matrix

The 5-Question Reboot Test

Template Structure

task_plan.md Template

findings.md Template

progress.md Template

Iron Laws

Anti-Patterns

The Manus Principles

planning-with-files

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Planning with Files - Manus-Style File-Based Planning

Core Principle

The 3-File Pattern

When to Use This Pattern

Critical Timing Rules

📌 At Task Start (SessionStart)

📌 Before Major Decisions (PreToolUse)

📌 After File Operations (PostToolUse)

Planning with Files - Manus-Style File-Based Planning

Core Principle

The 3-File Pattern

When to Use This Pattern

Critical Timing Rules

📌 At Task Start (SessionStart)

📌 Before Major Decisions (PreToolUse)

📌 After File Operations (PostToolUse)

📌 Before Task End (Stop)

The 6 Critical Rules

1. Create Plan First

2. The 2-Action Rule

3. Read Before Decide

4. Update After Act

5. Log ALL Errors

6. Never Repeat Failures

The 3-Strike Error Protocol

File Purposes

Read vs Write Decision Matrix

The 5-Question Reboot Test

Template Structure

task_plan.md Template

findings.md Template

progress.md Template

Iron Laws

Anti-Patterns

The Manus Principles