Execution plans¶
Small, reversible changes need a brief task-local plan and verification result.
For work across boundaries or multiple sessions, create a committed plan in docs/exec-plans/active/.
Use YYYY-MM-DD-short-name.md as its filename.
Plan contents¶
Include these sections:
- Objective and observable acceptance criteria.
- Scope, constraints, and links to the relevant code and product spec.
- Ordered steps with verification for each meaningful change.
- Progress and decisions, including why an approach changed.
- Validation results, blockers, and remaining work.
Keep the plan current as work proceeds. Preserve enough context for another agent to continue.
When all acceptance criteria pass, move the plan to completed/ and update this index.
Move deferred gaps into technical debt with an owner and exit criterion.
Active plans¶
Imported feature plans keep their original filenames and task lists. Feature IDs group related execution records. An earlier release does not close unfinished work. The inventory remains the source of status evidence.
| Feature | Execution records |
|---|---|
| Claude Serve & Deploy Parity | 024-claude-serve-deploy |
| Eval Runs & Test View Dashboard | 031-eval-runs-dashboard |
| Test Optimizer | 033-holodeck-test-optimizer |
| Production Hardening | 034-production-hardening |
| Dependency Stack Revamp (Semantic Kernel removal) | Implementation complete 2026-11-10; live evidence open, so the plan stays active. Execution plan; records |
| OpenAI Agents SDK Backend | Completion execution plan; historical records |
Drafts without an execution plan yet: 037, 041.
Completed and archived plans¶
- 2026-09-06: Spec and plan drift reconciliation
- 2026-09-06: Specification migration and custom command removal
- 2026-09-06: Harness engineering adoption
Frozen historical plans share completed/ but are explicitly labeled archived. They do not represent completed implementation.
| Feature | Disposition | Execution records |
|---|---|---|
| CLI & Core Agent Engine | Completed | 001-cli-core-engine |
| Init Agent Project | Completed | 004-init-agent-project |
| Global Settings & Response Format | Completed | 005-global-settings-response-format |
| Agent Test Execution | Completed | 006-agent-test-execution |
| Interactive Chat | Completed | 007-interactive-chat |
| Unstructured Vector Ingestion & Search | Completed | 008-unstructured-vector-ingestion-search |
| Interactive Init Wizard | Completed | 011-interactive-init-wizard |
| DeepEval Metrics | Completed | 012-deepeval-metrics |
| MCP CLI Command Group | Completed | 013-mcp-cli |
| Structured Data Ingestion | Completed | 014-structured-data-ingestion |
| Agent Local Server | Completed | 017-agent-local-server |
| OTel Observability | Completed | 018-otel-observability |
| Deploy Command | Completed | 019-deploy-command |
| HierarchicalDocumentTool | Completed | 020-structured-document-tool |
| Native Claude Agent SDK | Completed | 021-claude-agent-sdk |
| OTel GenAI Semconv in Claude Backend | Completed | 022-otel-genai-semconv |
| Async Tool Init Endpoints | Completed | 025-tool-init-endpoints |
| Subagent Orchestration | Completed | 029-subagent-orchestration |
| Multi-Turn Test Cases & Evaluators | Completed | 032-multi-turn-test-cases |
| Optimizer Progress Stream | Completed | 038-optimizer-progress-stream |
| HoloDeck Agents on Temporal | Completed | 040-holodeck-temporal |
| Ollama Endpoint Support | Archived / superseded by Claude-backend routing (021) | 009-ollama-endpoint-support |
| MCP Tool Operations | Archived / superseded by 021 and 035 MCP paths | 010-mcp-tool-operations |
| Vectorstore Reranking | Archived / folded into 020 | 015-vectorstore-reranking |
| GraphRAG Integration | Archived / not scheduled | 016-graphrag-integration |
| Choose Your Backend (ADK + MAF) | Archived / superseded by 035 and 042 | 023-choose-your-backend |
| Deterministic Spine | Archived / superseded by 040 | 036-deterministic-spine |
| GraphRAG Integration Plan (legacy) | Archived / superseded by 016, itself archived | graph-rag-integration |
Completed rows whose remaining scope lives in GitHub issues (014, 017, 018, 019, 020) name those issues in the inventory. Specs 039 (policy generator) and 023 are archived in the inventory; 039 never had an execution plan.
Relationship to feature specs¶
The product-spec index links canonical feature requirements in docs/product-specs/.
Research and design records live in docs/design-docs/<feature>/. Plans and task lists live in their execution-plan directory.
New specs use the format established by spec 040.
An execution plan links the relevant spec instead of copying its requirements.
When feature status changes, update docs/product-specs/inventory.md as well.
Earlier plans remain historical artifacts. Repository custom commands and their scaffolding have been removed.
Maintain specifications, design documents, and execution plans directly in the directories above.
Keep AGENTS.md as the knowledge map and CLAUDE.md as its single import.
Migration ledger¶
The migration ledger records one destination for each of the 316 original files. When a migrated file moves again, update its destination in the ledger and its index links. Source hashes record the migration baseline. They do not freeze future content edits.