alex
204bbb4c84
Remove the megamemory MCP knowledge graph and replace with plain markdown files in .memory/ for tracking plans, research, knowledge, and implementation state. This enables collaboration across people and agentic coding tools (Claude Code, Copilot, Cursor, etc.). Changes: - Remove megamemory MCP from opencode.jsonc - Delete tool/megamemory.ts and .megamemory/ database - Rewrite all 25 config files to use .memory/ markdown files - Add cross-tool instruction file awareness (AGENTS.md, CLAUDE.md, copilot-instructions.md, .cursorrules) - Update save-memory, bootstrap-memory, status commands for md workflow - Update all agent files, skills, and commands consistently
1.9 KiB
description
| description |
|---|
| Trigger phased planning for a new task — enters CLARIFY mode and walks through DISCOVER → PLAN → CRITIC-GATE |
You are the lead agent. The user has invoked /plan to begin structured planning for a task.
Steps
-
CLARIFY: Ask the user clarifying questions about the task using the
questiontool. Gather: goals, constraints, affected areas, success criteria. Record in the relevant plan file. -
DECOMPOSE (if applicable): If the user requested 3+ features, or features span independent domains/risk profiles, load the
work-decompositionskill. Follow its decomposition procedure to:- Identify distinct features and assess independence
- Group into independent workstreams
- Classify risk profiles and assign quality tiers
- Allocate worktrees (one per independent workstream)
- Identify human checkpoint triggers (security, architecture, vision-dependent features)
- Present the decomposition to the user and wait for approval before proceeding
-
DISCOVER: Delegate to
explorerto map relevant parts of the codebase. Delegate toresearcherfor any technical unknowns. Record findings in the relevant.memory/files. -
CONSULT (if needed): For domain-specific questions, check
.memory/decisions.mdfor cached SME guidance first. If not cached, delegate tosme. -
PLAN: Draft a phased task list per workstream. Each task must have: description, acceptance criteria, assigned agent(s), dependencies, workstream assignment, and coder dispatch scope (one feature per coder). Store the plan in
.memory/plans/<feature>.md. -
CRITIC-GATE: Delegate plan to
critic. If APPROVED → present plan to user and await go-ahead. If REPHRASE → revise and re-gate. If RESOLVE → stop, resolve every blocker, then re-gate. Do not proceed to EXECUTE with unresolved blockers.
Present the final approved plan to the user before starting EXECUTE.