planning-with-files vs IntelliCode
Side-by-side comparison to help you choose.
| Feature | planning-with-files | IntelliCode |
|---|---|---|
| Type | Workflow | Extension |
| UnfragileRank | 43/100 | 40/100 |
| Adoption | 0 | 1 |
| Quality | 1 | 0 |
| Ecosystem |
| 1 |
| 0 |
| Match Graph | 0 | 0 |
| Pricing | Free | Free |
| Capabilities | 13 decomposed | 6 decomposed |
| Times Matched | 0 | 0 |
Implements a three-file markdown-based external memory system (task_plan.md, findings.md, progress.md) that persists across AI agent context window resets and session boundaries. The system treats the filesystem as non-volatile disk storage analogous to RAM, automatically serializing agent state, decisions, and discoveries to markdown files that survive /clear commands and context loss. Each file serves a distinct purpose: task_plan.md tracks phases and decisions, findings.md captures research and technical decisions, progress.md logs session history and test results.
Unique: Uses filesystem-as-disk pattern inspired by Manus AI ($2B Meta acquisition) to solve context window volatility by treating three markdown files as persistent external working memory that survives agent session resets, context clears, and token limit exhaustion — a fundamental architectural shift from stateless to stateful agent design.
vs alternatives: Unlike vector databases or RAG systems that require external infrastructure, this approach uses plain markdown files as the persistence layer, making it zero-dependency, fully auditable, and git-compatible while solving the core problem of volatile AI context that traditional memory systems don't address.
Enforces a structured markdown schema across three files with specific sections and update frequencies: task_plan.md tracks phases, decisions, and error logs (updated after phase completion); findings.md captures research discoveries and technical decisions (updated every 2 view/browser operations); progress.md logs session history and test results (updated throughout session). Each file has a defined structure with headers, status indicators, and timestamp tracking, creating a queryable state representation that agents can read before deciding on next actions.
Unique: Defines a three-file markdown schema with specific update frequencies and section structures (task_plan.md phases, findings.md discoveries, progress.md logs) that creates a queryable state representation agents can read before deciding, rather than relying on implicit context or unstructured notes.
vs alternatives: More structured than free-form notes but simpler than database schemas, making it human-readable, git-diffable, and agent-queryable without requiring external infrastructure or complex parsing logic.
Decomposes complex tasks into explicit phases tracked in task_plan.md with status indicators (not-started, in-progress, complete, blocked). Each phase has a clear objective, success criteria, and dependencies on prior phases. The system uses phase boundaries to scope context windows, create git checkpoints, and trigger state updates. Agents read the current phase from task_plan.md before deciding on actions, ensuring work stays focused on the current phase rather than drifting across multiple objectives. Phase completion triggers automatic updates to task_plan.md and can trigger git commits, creating explicit checkpoints in the project history.
Unique: Treats phase-based decomposition as a first-class pattern with explicit status tracking in task_plan.md, using phase boundaries to scope context windows, create git checkpoints, and trigger state updates — making task structure explicit and queryable rather than implicit in agent context.
vs alternatives: Unlike implicit task decomposition in agent prompts which is lost on context reset, this approach makes phases explicit in markdown files with status tracking, enabling agents to understand task structure and current progress even after session interruptions or context resets.
Maintains findings.md as a searchable reference of research discoveries, technical decisions, and their rationale. Agents update findings.md after every 2 view/browser operations or significant discoveries, recording: what was discovered, why it matters, what decision was made, and what alternatives were considered. This creates a queryable knowledge base that agents can reference before making similar decisions, avoiding redundant research and enabling consistent decision-making across sessions. Findings are organized by topic or decision category, making them searchable without requiring full file reads. The pattern enables agents to build institutional knowledge that persists across sessions and can be shared with other agents.
Unique: Treats findings.md as a queryable knowledge base of discoveries and decisions that agents can reference before making similar choices, enabling consistent decision-making and avoiding redundant research across sessions — making institutional knowledge explicit and persistent.
vs alternatives: Unlike context-based knowledge which is lost on context reset, findings.md provides persistent, searchable reference of discoveries and decisions that agents can query without re-running research, enabling knowledge accumulation and sharing across sessions and agents.
Maintains progress.md as a session log that records all actions taken, test results, and session history throughout the agent's work. Entries are timestamped and include: what action was taken, what the result was, what was learned, and what comes next. Progress.md grows throughout the session and serves as a detailed audit trail of everything the agent did. Unlike task_plan.md (which tracks phases) and findings.md (which tracks discoveries), progress.md tracks the moment-by-moment execution history. This enables agents to review what was attempted in prior sessions, understand why certain approaches were taken, and avoid repeating failed attempts.
Unique: Maintains progress.md as a detailed, timestamped execution log that records every action, result, and learning throughout the session, creating a complete audit trail that enables agents to understand prior session context and avoid repeating failed attempts — treating execution history as a first-class artifact.
vs alternatives: Unlike generic logs which are often discarded or archived, progress.md is a persistent, queryable record that agents can reference to understand prior session context and execution history, enabling learning from past attempts and detailed debugging of agent behavior.
Implements a critical workflow pattern where agents must read the three markdown files (task_plan.md, findings.md, progress.md) before making decisions or taking actions. This pattern breaks the stateless agent loop by forcing agents to check current state, previous decisions, and error history before proceeding. The pattern is enforced through hook system automation and critical rules that prevent agents from acting without first consulting the persistent state files, creating a synchronous decision-making loop tied to filesystem state.
Unique: Enforces a synchronous read-before-decide loop where agents must consult persistent markdown state files before taking actions, breaking the stateless agent pattern by making every decision dependent on querying the filesystem state rather than relying on volatile context window memory.
vs alternatives: Unlike prompt-based context injection which loses state on context reset, this pattern makes state queries mandatory and persistent, ensuring agents always have access to the latest findings and decisions regardless of context window size or session boundaries.
Enables agents to recover from context window resets, /clear commands, or session interruptions by reading the three markdown files to reconstruct the prior session state. When a session resumes, the agent reads task_plan.md to identify the last completed phase, findings.md to understand prior discoveries and decisions, and progress.md to review session history and test results. This restoration process reconstructs the agent's understanding of project state without re-running prior work, allowing seamless continuation from the last known checkpoint.
Unique: Treats markdown files as persistent checkpoints that survive context window resets, enabling agents to reconstruct full project state from disk without re-running prior work — a fundamental shift from stateless to stateful agent design that makes context window exhaustion recoverable rather than fatal.
vs alternatives: Unlike traditional RAG or vector database recovery which requires external infrastructure and loses fine-grained decision context, this approach uses plain markdown files as checkpoints, making recovery deterministic, auditable, and git-compatible while preserving full decision history.
Integrates git commits as explicit checkpoints in the agent workflow, allowing agents to create git snapshots after completing phases or achieving milestones. The workflow uses git commits to mark stable states in the three markdown files and project code, enabling rollback to prior states if errors are discovered. Agents can reference git commit hashes in task_plan.md and progress.md, creating a version-controlled audit trail of state changes. This pattern combines filesystem persistence with git's version control, providing both recovery and history tracking.
Unique: Combines filesystem-based markdown persistence with git version control, using git commits as explicit checkpoints that mark stable states in both code and agent state files, enabling rollback and audit trails that neither filesystem persistence nor git alone provides.
vs alternatives: Stronger than markdown-only persistence because git provides immutable history and rollback capability; stronger than git-only because markdown files provide human-readable state snapshots that survive git operations and enable agent state recovery without code changes.
+5 more capabilities
Provides AI-ranked code completion suggestions with star ratings based on statistical patterns mined from thousands of open-source repositories. Uses machine learning models trained on public code to predict the most contextually relevant completions and surfaces them first in the IntelliSense dropdown, reducing cognitive load by filtering low-probability suggestions.
Unique: Uses statistical ranking trained on thousands of public repositories to surface the most contextually probable completions first, rather than relying on syntax-only or recency-based ordering. The star-rating visualization explicitly communicates confidence derived from aggregate community usage patterns.
vs alternatives: Ranks completions by real-world usage frequency across open-source projects rather than generic language models, making suggestions more aligned with idiomatic patterns than generic code-LLM completions.
Extends IntelliSense completion across Python, TypeScript, JavaScript, and Java by analyzing the semantic context of the current file (variable types, function signatures, imported modules) and using language-specific AST parsing to understand scope and type information. Completions are contextualized to the current scope and type constraints, not just string-matching.
Unique: Combines language-specific semantic analysis (via language servers) with ML-based ranking to provide completions that are both type-correct and statistically likely based on open-source patterns. The architecture bridges static type checking with probabilistic ranking.
vs alternatives: More accurate than generic LLM completions for typed languages because it enforces type constraints before ranking, and more discoverable than bare language servers because it surfaces the most idiomatic suggestions first.
planning-with-files scores higher at 43/100 vs IntelliCode at 40/100. planning-with-files leads on quality and ecosystem, while IntelliCode is stronger on adoption.
Need something different?
Search the match graph →© 2026 Unfragile. Stronger through disorder.
Trains machine learning models on a curated corpus of thousands of open-source repositories to learn statistical patterns about code structure, naming conventions, and API usage. These patterns are encoded into the ranking model that powers starred recommendations, allowing the system to suggest code that aligns with community best practices without requiring explicit rule definition.
Unique: Leverages a proprietary corpus of thousands of open-source repositories to train ranking models that capture statistical patterns in code structure and API usage. The approach is corpus-driven rather than rule-based, allowing patterns to emerge from data rather than being hand-coded.
vs alternatives: More aligned with real-world usage than rule-based linters or generic language models because it learns from actual open-source code at scale, but less customizable than local pattern definitions.
Executes machine learning model inference on Microsoft's cloud infrastructure to rank completion suggestions in real-time. The architecture sends code context (current file, surrounding lines, cursor position) to a remote inference service, which applies pre-trained ranking models and returns scored suggestions. This cloud-based approach enables complex model computation without requiring local GPU resources.
Unique: Centralizes ML inference on Microsoft's cloud infrastructure rather than running models locally, enabling use of large, complex models without local GPU requirements. The architecture trades latency for model sophistication and automatic updates.
vs alternatives: Enables more sophisticated ranking than local models without requiring developer hardware investment, but introduces network latency and privacy concerns compared to fully local alternatives like Copilot's local fallback.
Displays star ratings (1-5 stars) next to each completion suggestion in the IntelliSense dropdown to communicate the confidence level derived from the ML ranking model. Stars are a visual encoding of the statistical likelihood that a suggestion is idiomatic and correct based on open-source patterns, making the ranking decision transparent to the developer.
Unique: Uses a simple, intuitive star-rating visualization to communicate ML confidence levels directly in the editor UI, making the ranking decision visible without requiring developers to understand the underlying model.
vs alternatives: More transparent than hidden ranking (like generic Copilot suggestions) but less informative than detailed explanations of why a suggestion was ranked.
Integrates with VS Code's native IntelliSense API to inject ranked suggestions into the standard completion dropdown. The extension hooks into the completion provider interface, intercepts suggestions from language servers, re-ranks them using the ML model, and returns the sorted list to VS Code's UI. This architecture preserves the native IntelliSense UX while augmenting the ranking logic.
Unique: Integrates as a completion provider in VS Code's IntelliSense pipeline, intercepting and re-ranking suggestions from language servers rather than replacing them entirely. This architecture preserves compatibility with existing language extensions and UX.
vs alternatives: More seamless integration with VS Code than standalone tools, but less powerful than language-server-level modifications because it can only re-rank existing suggestions, not generate new ones.