Plan Feature: Comprehensive Archon Implementation Planning

---

description: Create a comprehensive implementation plan for an Archon feature argument-hint:

Plan Feature: Comprehensive Archon Implementation Planning

Objective

Produce a detailed, actionable implementation plan for: **$ARGUMENTS**

The plan will be saved to `.claude/archon/plans/{kebab-case-name}.md` and is designed to be consumed by the `/execute` command.

---

Phase 1: Feature Understanding

Restate the feature request in your own words. Identify:

1. Problem being solved — What user pain point or capability gap does this address?
2. Success criteria — What does "done" look like? How will we verify it works?
3. Scope boundaries — What is explicitly in scope vs. out of scope?
4. Package impact — Which of the 8 packages are affected? (paths, git, isolation, workflows, core, adapters, server, web)
5. Interface changes — Does this touch IPlatformAdapter, IAgentProvider, IDatabase, or IWorkflowStore? New interfaces needed?

---

Phase 2: Codebase Intelligence

Use subagents to perform targeted codebase research in parallel. Spawn separate subagents for:

**Subagent A — Affected package deep-dive:** Read all relevant source files in the affected packages. Map the current data flow. Identify every file that will need to change.

**Subagent B — Interface and type contracts:** Read `packages/core/src/types/` and relevant `index.ts` exports. Understand what interfaces exist and how they're consumed across packages.

**Subagent C — Test patterns:** Find existing test files similar to the area of change:

find packages/ -name "*.test.ts" | head -30

Read 2-3 representative test files to understand mocking patterns, assertion style, and `mock.module()` isolation requirements per package.

**Subagent D — Related prior work:**

git log --oneline --all | head -20

Read recent commits touching relevant files to understand change patterns.

Synthesize findings: current state, gaps, constraints.

---

Phase 3: External Research (if needed)

If the feature involves external APIs, new libraries, or unfamiliar patterns, use web search to research:

• Relevant SDK documentation
• Known gotchas or version incompatibilities
• Community patterns for the problem domain

Document any specific findings that affect the implementation approach.

---

Phase 4: Strategic Thinking

Before writing tasks, reason through:

**Architecture decisions:**

• Where does this logic belong? Apply SRP — keep each module focused on one concern.
• Does this require a new package, or extends an existing one?
• What's the dependency direction? Never create circular deps (paths ← git ← isolation/workflows ← core ← adapters ← server).

**Interface design:**

• Prefer extending existing narrow interfaces over creating fat ones.
• New interface methods only if they have a concrete current caller.
• Avoid adding methods to IPlatformAdapter or IAgentProvider unless e