Instruction file imported from Mao-pcdue/MyAI (.cursor/rules/05-milestones-and-phases.mdc). Copyright stays with the author.

Milestones and phases

The full plan lives in docs/ROADMAP.md. It defines v1.0 (kernel + brain + omnibar + intent + MCP plugins + one integration) and v1.5 (memory tree + voice + skills sandbox).

Boot check

At session start, after identifying the operator, read docs/ROADMAP.md and determine the active phase. The active phase is the first phase that has unfinished tasks.

Stay in phase

• Propose work that belongs to the active phase. Do not start phase N+1 work while phase N is incomplete.
• If the operator asks for work that belongs to a later phase, say so in one line and offer two options:
  1. Defer it until the current phase finishes.
  2. Mark it as an explicit "out-of-phase" exception in the research note and proceed.
• Never silently start out-of-phase work.

Updating the roadmap

When a phase task is genuinely complete (code shipped, tests pass, audit passes):

1. Mark it complete in docs/ROADMAP.md with a one-line note (date, branch, brief outcome).
2. If the completion changes the active phase, surface that in the next response so the operator knows.
3. Do not silently re-scope or delete unfinished tasks.

Adding tasks

New tasks are appended to the current phase's "Discovered" subsection, not retro-fitted into already-completed work. If a new task is large enough to need its own phase, propose a new phase in the research note before adding it.