What do I need to use Fortnightly Release Planner?

The backlog; Hours available per fortnight; Current version; Users' top complaints or requests; Fixed dates.

Is Fortnightly Release Planner free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Fortnightly Release Planner

Q: How do I know the Fortnightly Release Planner output is good?

The skill verifies itself against its own quality checks: Every release has a single theme of three to six words; Planned hours per release are at most 80% of the hours available; No item larger than half a fortnight remains unsplit; Every release lists what was left out on purpose.

🔵 Stable🕐 updated 2026-10-04 ✅ 4.8/5 🔷 SkillSpec L3 pm-oss-launch

Use when asked to plan releases for a side project or small open-source repo, turn a backlog into a release schedule, ship smaller and more often, or write a ROADMAP.md. Turns a backlog into small themed two-week releases and produces ROADMAP.md, a theme and scope for each release with what is deliberately left out, and a changelog template. For a stakeholder roadmap narrative inside a company, use roadmap-narrative.

▶ Run it free — no key needed 📝 Grade your existing draft 📱 Use as an app View SKILL.md ↗ What changed

🗣 Say this to your agent

“Turn my backlog into a release plan, I have about 6 hours a fortnight.”“Write a ROADMAP.md for my side project.”“Help me ship smaller releases more often.”“Plan the next few releases of my open-source library with themes.”

What to give it

▸The backlog — issues, ideas and bugs, in any form

▸Hours available per fortnight — , honestly

▸Current version — and versioning scheme (semantic versioning or dates)

▸Users' top complaints or requests — , if known

▸Fixed dates — a conference talk, a dependency deprecation, a launch post

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every release has a single theme of three to six words

✓Planned hours per release are at most 80% of the hours available

✓No item larger than half a fortnight remains unsplit

✓Every release lists what was left out on purpose

✓Fixed dates from the inputs are honoured in the plan

✓ROADMAP.md has a "Not planned" list with reasons

✓The changelog template uses the Added, Changed, Fixed and Removed headings

⚠️ What it refuses to do

**The kitchen-sink release.** A release with six unrelated features has no story and slips.

**Planning at 100% of capacity.** Bugs and reviews always arrive; plan to 80%.

**Dates on everything.** "Later" items with dates become broken promises.

**Skipping the changelog.** Users judge a project's health by its recent releases.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="fortnightly-release-planner"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Fortnightly Release Planner is one of 1307 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog