From 4e5144e225cef645fc2b9ea46b0fc91468a1d8f4 Mon Sep 17 00:00:00 2001 From: Jeffrey Phillips Freeman Date: Fri, 6 Feb 2026 15:49:50 -0500 Subject: [PATCH] docs: no longer reference plandex --- implementation_plan.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/implementation_plan.md b/implementation_plan.md index 075ac427b7..36cc12ee37 100644 --- a/implementation_plan.md +++ b/implementation_plan.md @@ -3,8 +3,7 @@ ## **CRITICAL**: Execute These Rules Without Exception - **Strictly adhere to guidelines in `./CONTRIBUTING.md`**: All rules and guidelines outlined in this file must be strictly followed at all times. - **Python implementation scope only**: Every action described here pertains to building an idiomatic Python codebase that implements the CleverAgents architecture. -- **Respect the reference**: Never modify any file inside `./plandex/`. Treat it purely as a read-only source of truth while building Python counterparts. This directory is TEMPORARY and will be deleted once migration is complete. -- **NO BACKWARDS COMPATIBILITY**: CleverAgents is a NEW standalone project. Do NOT maintain any backwards compatibility with Plandex. No migration guides, no compatibility shims, no support for Plandex configurations or data. +- **NO BACKWARDS COMPATIBILITY**: CleverAgents is a NEW standalone project. Do NOT maintain any backwards compatibility. No migration guides, no compatibility shims, no support for old configurations or data. - **Living document protocol**: After finishing each checklist item (and its testing sub-items), immediately append every decision, discovery, open question, or deviation to this document under the matching Notes section. This plan remains the authoritative record. - **Single documentation surface**: Do not create auxiliary notes elsewhere unless explicitly required. All architectural updates, troubleshooting outcomes, and contextual knowledge must flow back into this markdown file. - **Sequential discipline**: Always begin with the first unchecked item in the checklist. Do not progress until that item, its documentation update, and its testing sub-items (including any spawned remediation tasks) are fully resolved. @@ -17,7 +16,6 @@ - **Traceability requirement**: When a decision impacts future work, reference the relevant functions or modules in the Notes section using the `file_path:line_number` pattern for fast navigation. - **unit tests coverage above 85% at all times**: unit test coverage must remain above 85% at all times. Unit tests can be run with `nox -e unit_tests` and is run as part of the default test suite run with `nox`. - **must be statically typed**: All code at all times must use statically typed typing and must pass the static check run with `nox -e typecheck` which is run as part of the default test suite with `nox`. Under no circumstances at no point should you ignore type checking, this means never turn it off in the config files, and never use inline comments to force an type checking error to be suppressed. -- **NO PLANDEX REFERENCES**: All environment variables must use CLEVERAGENTS_ prefix, not PLANDEX_. No references to Plandex should exist in the final code. CleverAgents is a standalone project, not a fork or migration. - **Use existing tooling**: Always prefer nox sessions over raw commands, Behave for unit tests over new frameworks, Robot for integration tests, Hatch for dependency management. - **Mock placement rule**: ALL mocks, test doubles, and mock implementations MUST exist only in `features/` directory. Production code in `src/` and utility scripts in `scripts/` must NEVER contain mock implementations, test data, or conditional testing behavior. Use dependency injection to swap implementations during tests. - **CRITICAL - Implementation Checklist Separation**: The "Implementation Checklist" section MUST always remain separate and be the LAST section of this document. All development notes, design decisions, progress updates, technical details, and discoveries belong in their respective phase Notes sections (e.g., Phase 0 Notes, Phase 1 Notes, Phase 2 Notes) which appear BEFORE the Implementation Checklist. Never add content after the checklist section. The checklist is for tracking what needs to be done; the Notes sections are for documenting what was done and how. @@ -69,11 +67,9 @@ While CleverAgents leverages LangGraph and LangChain for the underlying LLM runt - Ship a Python-based, feature-complete application named **CleverAgents** implementing the four-phase plan lifecycle with actors, projects, resources, and sandbox-based execution. - Implement functionality using Pythonic architecture: dependency inversion, strategy, adapter, observer, state, builder, factory, template method, event sourcing, and decorator patterns where appropriate. - Build a unified Python executable (`agents`) that supports both in-process single-user mode and `agents serve --port ` multi-user deployments without cloud dependencies. -- Use only CleverAgents/CleverThis branding throughout the entire codebase - no Plandex references should exist in the final product. - Enforce fail-fast error handling, rich logging, and comprehensive type coverage with docstrings and runtime validation aligned to Python best practices. - Provide a pluggable ORM abstraction supporting heavy (PostgreSQL/MySQL) and lightweight (SQLite/DuckDB/in-memory) backends, with zero-code configuration switches. - Generate fresh documentation via Docusaurus integrated within the `docs/` directory of the CleverAgents project. -- Delete the plandex/ reference directory once migration is complete - it serves only as temporary reference material. ### Core Architectural Requirements