phase-planning

浏览 Phoenix 项目路线图，了解当前所处阶段的进展，规划下一步任务，并追踪尚待完成的工作。适用于用户询问接下来该做些什么、当前项目状态如何、阶段推进情况如何、路线图规划如何、任务安排怎样，或是还有哪些工作尚未完成时使用。

SKILL.md

--- frontmatter

name: phase-planning
description: Navigate the Phoenix project roadmap, understand current phase status, plan next tasks, and track what needs to be done. Use when user asks what to work on next, current project status, phase progress, roadmap, task planning, or what's left to do.

Phase Planning — Phoenix Agentic Engine Interface

Repo Context

This is the Interface SDK (TypeScript). It defines contracts between Engine and Backend.

Current Status

•Phase 1 foundation: Complete — fixtures, typed SDK, transport, validators, tests

Next steps

•Keep contract fixtures in sync as backend evolves
•Add WebSocket transport support for real-time streaming (Phase 5+)
•Add v2 contract namespace when breaking changes are needed
•Expand test coverage for edge cases
•Publish as npm package when ready for external consumption

How Interface fits into project phases

Phase	Interface involvement
Phase 0	Complete — contracts, SDK, tests
Phase 1	Engine integrates SDK into adapter layer
Phase 2	Add delta sync transport, sequence validation
Phase 3	Add tool invocation contract types
Phase 4	Add parallel plan / worktree contract types
Phase 5+	WebSocket streaming, advanced transport

Key deliverables this repo owns

•contracts/v1/*.json — golden fixture mirrors
•sdk/client/PhoenixClient.ts — typed HTTP client
•sdk/client/types.ts — request/response TypeScript types
•sdk/transport/ — HTTP transport with retry/backoff
•sdk/validators/ — Zod validation schemas
•tests/contract/ — fixture validation tests
•tests/compatibility/ — SDK compatibility tests

Working principles

•Stay protocol-only — no UI, no orchestration, no business logic
•Contract compatibility is non-negotiable
•Keep dependencies minimal
•Both Engine and Backend depend on this repo
•Test edge cases — malformed payloads, network errors, retry exhaustion