.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation.
Install Launch Readiness
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills launch-readiness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch-readiness .claude/skills/launch-readiness && rm -rf skills-srcUse ~/.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/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .claude/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readinessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills launch-readiness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch-readiness .agents/skills/launch-readiness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .agents/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills launch-readiness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch-readiness .cursor/skills/launch-readiness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .cursor/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/launch-readiness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills launch-readiness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch-readiness .gemini/skills/launch-readiness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .gemini/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills launch-readinessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch-readiness .github/skills/launch-readiness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .github/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills launch-readiness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch-readiness .opencode/skills/launch-readiness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch-readiness" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/launch-readiness into .opencode/skills/launch-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-readiness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
launch-readiness- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 475 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation.
- Works in 5 steps: Review provided launch brief and… → Flag any incomplete items as blockers… → Assess overall readiness and produce… → …
- Preparing for any product
- SKILL.md covers Required Inputs, Readiness Checklist by Function, Process and Output Structure, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Launch Readiness is an agent skill from mohitagw15856/pm-claude-skills. Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.
Its SKILL.md is about 1k 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 Feature launches and release readiness. 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
- Preparing for any product
- Running a pre-launch review
- Determining whether a release is safe to ship
Example prompts
- “Use the launch-readiness skill to assess pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go…”
- “/launch-readiness”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Review provided launch brief and checklist responses
- Flag any incomplete items as blockers (must fix) or risks (monitor)
- Assess overall readiness and produce go/no-go recommendation with rationale
- If no-go, specify exactly what must be completed and by when
- Validate — Confirm every blocker has a named owner and resolution deadline, and that the rollback plan is tested (not just documented)
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.
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
Launch Readiness loads about 1k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 475 words of instructions outside code blocks.
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). 475 words, ~1,006 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-readiness/SKILL.md (or your agent's skills folder).- name
- launch-readiness
- description
- Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.
Launch Readiness Skill
Ensure nothing falls through the cracks before launch by systematically checking readiness across every function — and producing a clear, evidenced go/no-go recommendation.
Required Inputs
Ask the user for these if not provided:
- Launch name and target date
- Launch tier (Tier 1 = major launch / Tier 2 = significant feature / Tier 3 = incremental update)
- Completed checklist items or self-assessment (even partial is fine — we'll surface gaps)
- Team and role names (to assign owners to blockers)
Readiness Checklist by Function
Product & Engineering
- Feature complete against launch spec
- Performance benchmarks met
- Accessibility standards checked
- Edge cases documented and handled
- Rollback plan defined and tested
Marketing & Comms
- Launch messaging approved
- Blog post / press release drafted
- Social content prepared
- Email campaigns scheduled
- Landing page live and tested
Support & Success
- Support team trained on new feature
- FAQ and help docs published
- Escalation path defined for launch issues
- Customer success briefed (if enterprise)
Sales & Partnerships
- Sales enablement materials ready
- Pricing confirmed and communicated
- Partner comms sent (if applicable)
Data & Analytics
- Tracking events implemented and verified
- Launch metrics dashboard live
- Baseline metrics captured pre-launch
Process
- Review provided launch brief and checklist responses
- Flag any incomplete items as blockers (must fix) or risks (monitor)
- Assess overall readiness and produce go/no-go recommendation with rationale
- If no-go, specify exactly what must be completed and by when
- Validate — Confirm every blocker has a named owner and resolution deadline, and that the rollback plan is tested (not just documented)
Output Structure
Launch Readiness Assessment: [Feature/Product Name]
Launch Date: [date] Launch Tier: [1 / 2 / 3] Overall Status: ✅ Go / ⚠️ Conditional Go / 🛑 No-Go
Blockers (must resolve before launch):
- [item + owner + resolution required by]
Risks (monitor closely):
- [item + mitigation plan]
Ready Areas:
- [function]: ✅ Ready
Recommendation: [Clear go/no-go with rationale — 3-5 sentences]
Show full SKILL.md (185 more words)Show less
Quality Checks
- Every blocker has a specific owner (not "the team") and a deadline
- Rollback plan is explicitly tested, not just written
- Analytics events are verified in staging, not just implemented
- Go/No-Go decision has a named decision-maker and a cut-off time
- At least one post-launch monitoring check is scheduled (e.g., T+2hr, T+24hr)
Anti-Patterns
- Do not mark a function as "Ready" without evidence — green status must be backed by a completed checklist item, not an assumption
- Do not issue a Conditional Go without specifying exactly what conditions must be met and by when — vague conditions are not conditions
- Do not treat the rollback plan as complete unless it has been tested in staging, not just documented
- Do not assign blockers to "the team" — every blocker must have a single named owner or it will not be resolved before launch
- Do not skip the analytics verification step — unverified tracking events mean the launch will be invisible and cannot be evaluated
Example Trigger Phrases
- "Are we ready to launch?"
- "Run a pre-launch review."
- "Give me a go or no-go for this release."
- "Is this release safe to ship?"
© 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/launch-readiness of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Launch Readiness 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch Readiness this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar 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…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
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.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
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.
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.
Related
Categories
Questions about Launch Readiness
What does Launch Readiness do?
Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Launch Readiness is an agent skill from mohitagw15856/pm-claude-skills. Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation.
When should I use Launch Readiness?
Launch Readiness fits situations like: preparing for any product; running a pre-launch review; determining whether a release is safe to ship.
How do I install Launch Readiness in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a claude-code`. Or copy the skill folder (skills/launch-readiness in mohitagw15856/pm-claude-skills) into .claude/skills/launch-readiness in your project. Claude Code loads it when a task matches its description.
How do I install Launch Readiness in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill launch-readiness -a codex`. Or copy the skill folder (skills/launch-readiness in mohitagw15856/pm-claude-skills) into .agents/skills/launch-readiness in your project. Codex loads it when a task matches its description.
Can I use Launch Readiness 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 launch-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-readiness, .gemini/skills/launch-readiness, .github/skills/launch-readiness and .opencode/skills/launch-readiness in your project.
What does Launch Readiness need to run?
SKILL.md names no scripts, command-line tools or credentials: Launch Readiness is instructions for the agent only.
Does Launch Readiness 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 Launch Readiness 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 Launch Readiness use?
Launch Readiness 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 Launch Readiness use?
About 1k tokens (SKILL.md is roughly 4k 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 Launch Readiness?
Skills that share tags, products or a category with Launch Readiness: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Readiness?
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.