How do I install the Phase Planning skill?

Run npx skillmds@latest add rivie13/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: docs only. 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) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Phase Planning by rivie13 — Agent Skill

Name: Phase Planning
Rating: 4.2 (5 reviews)
Author: rivie13

Phase Planning

Navigate the Website Frontend 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 Website Frontend

Repo Context

This is the Website Frontend (Public). See docs/IMPLEMENTATION_PLAN.md for the full plan.

How to check roadmap

Read the planning docs for full details:

read_file("Phoenix-Agentic-Website-Frontend/docs/IMPLEMENTATION_PLAN.md")
read_file("Phoenix-Agentic-Website-Frontend/docs/ARCHITECTURE.md")
read_file("Phoenix-Agentic-Website-Frontend/.github/instructions/website-frontend-roadmap.instructions.md")

Key docs

File	Purpose
`docs/IMPLEMENTATION_PLAN.md`	Full implementation plan
`docs/ARCHITECTURE.md`	Frontend architecture
`docs/AUTOMATED_BLOG_PLAN.md`	Blog automation plan
`docs/SECURITY_BOUNDARY.md`	Security boundary rules
`docs/MAILCHIMP_SETUP.md`	Newsletter integration

Using VS Code tasks for development

website: dev: setup — Install npm dependencies
website: dev: run — Start Next.js dev server
website: dev: lint — Run ESLint
website: dev: typecheck — Run tsc --noEmit
website: dev: test — Run vitest
website: dev: build — Production build
website: dev: check — Full validation (lint + typecheck + test + build)
website: dev: clean — Remove build artifacts

Working principles

Read docs/ before starting any new feature area
Keep changes scoped to one feature/task at a time
Security boundary rules apply — no secrets in client-side code
Cross-service integration via API client, not direct backend coupling
Maintain SSR compatibility for all components

Frequently asked questions