Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Planning with Files
specialization:planning-with-filesa5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewarticlejsongraph
III.Related pagespp. 1 - 1
II.
Specialization reference

specialization:planning-with-files

Reading · 3 min

Planning with Files reference

Planning with Files is a persistent markdown-based planning methodology inspired by Manus AI's context engineering patterns. It treats the filesystem as extended memory for volatile agent workflows, solving the fundamental problem that agent context windows are ephemeral while file systems are persistent.

Specializationwiki/library/planning-with-files.mdOutgoing · 1Incoming · 2

Planning with Files

**Source:** Planning with Files by OthmanAdi **Category:** Persistent Markdown-Based Planning (Context Engineering) **Priority:** High

Overview

Planning with Files is a persistent markdown-based planning methodology inspired by Manus AI's context engineering patterns. It treats the filesystem as extended memory for volatile agent workflows, solving the fundamental problem that agent context windows are ephemeral while file systems are persistent.

Central Principle: "Context Window = RAM (volatile); Filesystem = Disk (persistent)"

Key Features

  • **Three-File Pattern** (task_plan.md, findings.md, progress.md) for structured persistence
  • **5 Manus Principles** (Filesystem as Memory, Attention Manipulation, Error Persistence, Goal Tracking, Completion Verification)
  • **2-Action Rule** for systematic findings capture
  • **Session Recovery** across context window resets
  • **Quality-Gated Convergence** with weighted scoring
  • **Never Repeat Failures** with error pattern detection and approach mutations

Process Files

FileDescriptionPrimary Agents
planning-orchestrator.jsFull lifecycle (plan, execute, verify)All agents
planning-session.jsSession lifecycle managementSession Manager, Plan Architect
planning-execution.jsTask execution with 2-action ruleExecution Monitor, Error Analyst, Findings Curator
planning-verification.jsCompletion verification and scoringCompletion Verifier, all analysis agents

Agent Personas

AgentRoleID
Plan ArchitectPlan Structure Designpwf-plan-architect
Execution MonitorTask Execution Oversightpwf-execution-monitor
Findings CuratorResearch & Discovery Managementpwf-findings-curator
Error AnalystError Analysis & Pattern Detectionpwf-error-analyst
Session ManagerSession Lifecycle Managementpwf-session-manager
Completion VerifierPhase Completion Verificationpwf-completion-verifier

Skills

SkillDescriptionAgent
Plan CreationStructured task_plan.md generationPlan Architect
Findings CaptureResearch persistence with 2-Action RuleFindings Curator
Progress TrackingSession logs and phase statusExecution Monitor
Error LoggingError persistence and pattern detectionError Analyst
Session RecoveryContext recovery across resetsSession Manager
Completion VerificationWeighted quality scoringCompletion Verifier

Three-File Pattern

task_plan.md

The plan file contains phases, goals, and progress checkboxes. It is created first (Rule 1: never start without a plan) and serves as the primary source of truth for what needs to be done.

findings.md

The findings file captures research, discoveries, and decision rationale. Updated via the 2-Action Rule (save findings after every 2 view/browser operations) to ensure nothing is lost.

progress.md

The progress file maintains session logs, test results, and error records. It supports session recovery by preserving timestamps and session identifiers.

5 Manus Principles

1. **Filesystem as Memory** - Store in files, not context window 2. **Attention Manipulation** - Re-read plan before every decision 3. **Error Persistence** - Log all failures in progress file 4. **Goal Tracking** - Checkboxes show progress at a glance 5. **Completion Verification** - Verify all phases before exit

Quality Scoring

ComponentWeightMeasurement
Phase Completion40%Checked goals / total goals
Error Resolution25%Resolved errors / total errors
Findings Coverage20%Phases with findings / total phases
Progress Continuity15%Sessions without gaps / total sessions

Examples

See examples/ directory for JSON input files covering various task types and configurations.

Article source

Planning with Files (Library)

This record inherits its article from a related Page node.

Related pages

Planning with Files (Library)

Shortcuts

Open overview
Open JSON
Open graph