A milestone lifecycle skill guides the end of one project milestone and preparation for the next. A milestone is a planned checkpoint in a project's progress.

Auditing the current milestone, closing gaps, archiving it, collecting deferred tasks, and creating the next phases.

It brings verification, archiving, unfinished work, and next-version planning into one guided flow.

lifecycle — Skill for Claude Code by Sh3rd3n/megazord

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Sh3rd3n/megazord --skill lifecycle

Clone the repo

git clone --depth 1 https://github.com/Sh3rd3n/megazord

Made for: Claude Code.

Or install mz, the plugin that ships this one along with the rest of its 16 skills, 16 commands, 6 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sh3rd3n/megazord/lifecycle/github.svg)](https://agentmods.dev/skills/sh3rd3n/megazord/lifecycle)

Your own site

<a href="https://agentmods.dev/skills/sh3rd3n/megazord/lifecycle"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/lifecycle/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sh3rd3n/megazord/lifecycle"><img src="https://agentmods.dev/badge/skills/sh3rd3n/megazord/lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,593 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.03593
Opus 5.5	$0.00007	$0.01437
Sonnet 5.5	$0.00004	$0.00719
Haiku 4.5	$0.00002	$0.00359

Measured 1mo ago against content hash bef6f7f7e6e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lifecycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/lifecycle/SKILL.md · 439 lines

How it starts

The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/mz:lifecycle

Orchestrate the full milestone lifecycle: audit verification status, archive the current milestone, collect deferred items, and prepare the next version. Uses existing CLI tools (milestone audit, milestone archive, milestone create, roadmap list, roadmap add-phase) as the execution backbone while providing a guided interactive experience.

Note: This skill handles the entire end-of-milestone flow in a single entry point. When audit finds gaps, it proposes gap-closure phases and exits. When audit passes, it proceeds through archive, deferred item collection, and next-version preparation.

Reference @skills/init/design-system.md for visual output formatting. Reference @skills/shared/presentation-standards.md for content formatting rules. Reference @skills/shared/terminology.md for official term definitions.

Output the stage banner:

+===============================================+
|  MEGAZORD > LIFECYCLE                         |
+===============================================+

Step 2: Load Context and Validate

Read .planning/megazord.config.json. If missing, display error and stop:

## Error

Project not initialized — no megazord.config.json found.

`/mz:init`

If config exists, continue loading:

Read .planning/STATE.md for current position.
Read .planning/ROADMAP.md for phase details.
Read .planning/MILESTONE.md if it exists (for version detection and phase scope).

Determine the plugin path for CLI commands:

Read plugin_path from the config JSON.
If plugin_path is not set in config, try ~/.claude/plugins/mz. Check if ~/.claude/plugins/mz/bin/megazord.mjs exists.
If neither exists, display error and stop:

## Error

Plugin path not configured.

`/mz:settings` to set plugin_path, or `/mz:init` to re-initialize.

Parse the user's message (text after /mz:lifecycle) for arguments:

--skip-audit -- bypass the audit step entirely (for informal projects)
{version} -- specify the milestone version to archive (optional; auto-detected from MILESTONE.md if present)

Read the full file on GitHub · 439 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 439 lines · 18 tokens per session scan A bef6f7f7e6e2

Subscribe to this mod's changes

lifecycle is a skill published in the GitHub repository Sh3rd3n/megazord (3 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 3,593 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Multi-Agent Planning Project management ai-agent claude-code-plugin cli code-quality

status

Maintain the repository's STATUS.md — the fixed-shape status file an external chief-of-staff agent reads to brief the founder. Applies to every session; update it in the same commit as the work and before the final message.

Evolvlabsai/Exolvra-Genesis · 48 tokens

recipe-plan

Create work plan from design document and obtain plan approval.

shinpr/claude-code-workflows · 13 tokens

Codex

Mission control: create tasks, assign to an agent/team, wait for human approval, worker runs in the background, accept results.

tubecreate/tubecli · 29 tokens

great_cto

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

avelikiy/great_cto · 32 tokens

opportunity-solution-tree

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…

avelikiy/great_cto · 71 tokens

done-blocked

Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.

avelikiy/great_cto · 51 tokens

lifecycle