Agent skill

Fortnightly Release Planner

by mohitagw15856 in mohitagw15856/pm-claude-skills

A skill your agent uses 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.

MITAuto-check passedProduct & Project Management

Install Fortnightly Release Planner

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill fortnightly-release-planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills fortnightly-release-planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fortnightly-release-planner .claude/skills/fortnightly-release-planner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fortnightly-release-planner
GitHub stars
1.4k
Token cost
~925 tokens
SKILL.md length
426 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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.

  • Works in 5 steps: Sized backlog → Release plan → ROADMAP.md → …
  • Asked to plan releases for a side project
  • SKILL.md covers Required Inputs, Output Structure, Quality Checks and Anti-Patterns, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fortnightly Release Planner is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Changelog and release notes. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to plan releases for a side project
  • Small open-source repo
  • Turn a backlog into a release schedule
  • Ship smaller and more often

Example prompts

  • “/fortnightly-release-planner”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Sized backlog
  2. Release plan
  3. ROADMAP.md
  4. Changelog template
  5. Release-day checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fortnightly Release Planner loads about 925 tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 426 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~925

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 426 words, ~925 tokens.

Download SKILL.mdSave it as .claude/skills/fortnightly-release-planner/SKILL.md (or your agent's skills folder).
name
fortnightly-release-planner
description
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.
version
1.0.0

Fortnightly Release Planner

Side projects stall when the next release is "when it is done": the scope grows, nothing ships, and users assume the project is abandoned. Small releases every two weeks, each with one theme, keep momentum and give users a reason to come back. This skill turns a backlog into a sequence of themed fortnightly releases that fit the time the maintainer actually has.

Required Inputs

Ask for these if not provided:

  • 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

Output Structure

1. Sized backlog

A table of every item with a size in hours and a value score: | Item | Type (bug, feature, docs, chore) | Size (hours) | User value (1 to 3) | Depends on |

Items over half the fortnight's hours are split before planning, and the split is shown.

2. Release plan

For each release, in order:

markdown
### v[x.y.0]: [Theme in three to six words]   (target: [date])
**Why this theme now:** [one sentence linked to a user need or fixed date]
**In:** [items, with sizes; total within 80% of the fortnight's hours]
**Out (on purpose):** [items that fit the theme but wait, and why]
**Done means:** [two or three observable results]

Plan four to six releases. Leave 20% of each fortnight unplanned for bugs and review.

3. ROADMAP.md

A ready-to-commit file with: a two-sentence statement of where the project is heading, the next three releases (theme, target date, three headline items each), a "Later" list without dates, and a "Not planned" list with one-line reasons.

4. Changelog template

A CHANGELOG.md section to copy for each release, following Keep a Changelog headings:

markdown
## [x.y.0] - YYYY-MM-DD
**Theme:** ...
### Added
### Changed
### Fixed
### Removed
5. Release-day checklist

Six to eight binary steps for shipping a release in under 30 minutes (tag, notes, publish, announce).

Show full SKILL.md (164 more words)Show less

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
  • 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

Anti-Patterns

  • 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.

Example Trigger Phrases

  • "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."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/fortnightly-release-planner of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Fortnightly Release Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fortnightly Release Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fortnightly Release Planner this skillmohitagw15856/pm-claude-skills1.4k—~925Automated safety check: PassMIT
Release Readiness Reviewkernitus/BukkitOldCombatMechanics225—~1.5kAutomated safety check: PassMPL-2.0
Roadmapcloudposse/atmos1.4k—~2.5kAutomated safety check: PassApache-2.0
Release ReadinessRunoreLab/MahoShojo-Generator166—~342Automated safety check: PassApache-2.0
Gf Releasecodejunkie99/Gateflow-Plugin117—~676Automated safety check: PassCustom licence
Abo Issue Verifyjeeftor/audiobook-organizer190—~499Automated safety check: PassMIT

Similar skills

  • Release Readiness Review

    kernitus/BukkitOldCombatMechanics

    A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…

    225 GitHub stars~1.5k tokensUpdated 7 days ago
    Product & Project ManagementAuto-check passed
  • Roadmap

    cloudposse/atmos

    Maintain and update the Atmos roadmap page (website/src/data/roadmap.js): milestone/initiative/quarter schema, progress-percentage math, the curated featured[] cap (max 6, never auto-modified), and…

    1.4k GitHub stars~2.5k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Release Readiness

    RunoreLab/MahoShojo-Generator

    A skill your agent uses when preparing or reviewing a MahoShojo-Generator version release, release candidate, changelog/docs readiness, deployment impact, migration notes, or final pre-release…

    166 GitHub stars~342 tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Gf Release

    codejunkie99/Gateflow-Plugin

    GateFlow release readiness workflow. An agent skill from codejunkie99/Gateflow-Plugin.

    117 GitHub stars~676 tokensUpdated 24 days ago
    Product & Project ManagementAuto-check passed
  • Abo Issue Verify

    jeeftor/audiobook-organizer

    Verify that an Audiobook Organizer issue is done by checking acceptance criteria, code changes, tests, docs, changelog, and ABS matrix obligations.

    190 GitHub stars~499 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Workflow

    waynesutton/markdown-site

    Project workflow for PRDs, task tracking, changelog sync, and documentation updates.

    627 GitHub stars~624 tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Fortnightly Release Planner

What does Fortnightly Release Planner do?

A skill your agent uses 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. Fortnightly Release Planner is an agent skill from mohitagw15856/pm-claude-skills.md.

When should I use Fortnightly Release Planner?

Fortnightly Release Planner fits situations like: asked to plan releases for a side project; small open-source repo; turn a backlog into a release schedule; ship smaller and more often.

How do I install Fortnightly Release Planner in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill fortnightly-release-planner -a claude-code`. Or copy the skill folder (skills/fortnightly-release-planner in mohitagw15856/pm-claude-skills) into .claude/skills/fortnightly-release-planner in your project. Claude Code loads it when a task matches its description.

How do I install Fortnightly Release Planner in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill fortnightly-release-planner -a codex`. Or copy the skill folder (skills/fortnightly-release-planner in mohitagw15856/pm-claude-skills) into .agents/skills/fortnightly-release-planner in your project. Codex loads it when a task matches its description.

Can I use Fortnightly Release Planner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill fortnightly-release-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fortnightly-release-planner, .gemini/skills/fortnightly-release-planner, .github/skills/fortnightly-release-planner and .opencode/skills/fortnightly-release-planner in your project.

What does Fortnightly Release Planner need to run?

SKILL.md names no scripts, command-line tools or credentials: Fortnightly Release Planner is instructions for the agent only.

Does Fortnightly Release Planner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fortnightly Release Planner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fortnightly Release Planner use?

Fortnightly Release Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fortnightly Release Planner use?

About 925 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fortnightly Release Planner?

Skills that share tags, products or a category with Fortnightly Release Planner: Release Readiness Review (kernitus/BukkitOldCombatMechanics, 225 stars), Roadmap (cloudposse/atmos, 1.4k stars), Release Readiness (RunoreLab/MahoShojo-Generator, 166 stars) and Gf Release (codejunkie99/Gateflow-Plugin, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fortnightly Release Planner?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.