How do I install the Phase Planning skill?

Run npx skillmds@latest add rivie13-phoenix-agentic-engine-interface/phase-planning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Phase Planning safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Phase Planning?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Phase Planning free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Phase Planning?

rivie13 (@rivie13-phoenix-agentic-engine-interface) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Phase Planning by rivie13-phoenix-agentic-engine-interface

Name: Phase Planning
Rating: 4.666666666666667 (3 reviews)
Author: rivie13

Phase Planning

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.

rivie13 Updated Sep 10, 2026

File contents

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

---name: phase-planningdescription: 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 ContextThis 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 principles1. Stay protocol-only — no UI, no orchestration, no business logic2. Contract compatibility is non-negotiable3. Keep dependencies minimal4. Both Engine and Backend depend on this repo5. Test edge cases — malformed payloads, network errors, retry exhaustion

Frequently asked questions