skills.rest
MoofonLi
MoofonLiCOMMUNITY
Explore all skills by this author →
GitHub

planning

Cuts a dev-ready version into ordered implementation phases and writes the version plan document.

2|Updated Jul 11, 2026
Search Tags:#requirements#roadmap#release planning#phase breakdown#technical lead#version planning#spec loop
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill planning-moofonli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/planning
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill planning-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a software version into coherent, dependency-ordered implementation phases is error-prone when done ad hoc. This Skill produces an authoritative version plan (docs/handoff/<version>/<version>-plan.md) that names concrete FRs, ADRs, source paths, and acceptance criteria so each phase's Spec Loop has a precise map to execute against. ## Core Features & Use Cases - Phase Cutting: Splits a version's functional requirements into independently reviewable phases ordered by dependency, with exactly one final phase shipping the release and naming the version bump. - Structured Plan Authoring: Writes each phase section with concrete change surfaces (catalog entries, src/dev_ready/... files, overlay/verify behavior), expected tests, and checkable acceptance criteria. - Standing Constraints Block: Restates binding rules from AGENTS.md (pins only in manifest.json, network only in fetch/, no-network unit tests, Conventional Commits) plus the four-command phase-end verification. - Use Case: When starting v0.4 of dev-ready, ask the agent to plan the version; it reads docs/version-plan.md, docs/requirements.md, ADRs, and the previous plan, then writes a phase-by-phase plan each Spec Loop (grill-with-docs → to-spec → to-tickets → implement) runs over. ## Quick Start Ask your coding agent to plan the next dev-ready version, for example: "plan v0.4 and break it into phases using the planning skill."

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a software version into implementation phases?▼

Read the roadmap and requirements docs, then cut phases as coherent, independently reviewable slices ordered by dependency, with foundational infrastructure before consuming features. Exactly one final phase ships the release and names the version bump.

What should a version plan document contain for each phase?▼

Each phase section needs a title with FR numbers, the concrete change surface (files, catalog entries, verify behavior), expected tests with tier constraints, and checkable acceptance criteria. Cross-phase couplings are stated as explicit exclusions.

Where is the dev-ready version plan stored and is it committed?▼

The plan lives at docs/handoff/<version>/<version>-plan.md and is gitignored per ADR-011, making it a working artifact rather than a committed repo doc. The committed source it draws from is docs/version-plan.md.

How does the version plan relate to the Spec Loop workflow?▼

Each phase is executed only through the Spec Loop: grill-with-docs, to-spec, to-tickets, then implement with review included. The plan is the map those loops run over, so phase sections name the FR each spec will cover.

What inputs must be read before writing a version plan?▼

Read docs/version-plan.md for scope, docs/requirements.md for exact FR text, docs/architecture.md and docs/decisions/ for binding ADRs, docs/cli-spec.md for flag changes, pyproject.toml for the baseline version, and the previous version's handoff plan.

Related Skills

Explore More Software Engineering Skills→
sakamotchisakamotchi
2

generate-project-docs

Generates standardized scaffolding for multi-phase project documentation in docs/projects/{project-name}.

Community
Advanced
scosmanscosman
42

spec

Orchestrate spec-driven planning, phased implementation, and spec-aware code review.

Community
Advanced
NSObjectsNSObjects
4

designing

Define architecture decisions and map requirements to technical approaches before planning.

Community
Advanced
sagittarassagittaras

file-issue

Creates a single ad hoc tracker issue as a Note with labels and confirmation.

Official
Advanced