agentmods.dev

feature-ship-cycle

feature-ship-cycle is a skill for Claude Code, Codex from uthumany/uthy-legacy-os. It costs 35 tokens per session (785 once invoked), scanned A, original, MIT.

An end-to-end workflow for taking a validated product idea from requirements and design through development, release, and review of its results.

In plain words
What is it for?
Use it to write a product requirements document, split work into development stories, define acceptance criteria, coordinate design and engineering, launch the feature, and measure its outcome.
Why use it?
It creates checkpoints between stages so unclear requirements or unfinished decisions are found before they cause rework.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 5repo 5mo ago A scan 35 tokens original MIT

Good fit Use it to write a product requirements document, split work into development stories, define acceptance criteria, coordinate design and engineering, launch the feature, and measure its outcome.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uthumany/uthy-legacy-os/feature-ship-cycle
View source ↗ uthumany/uthy-legacy-os uthumany.github.io
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 uthumany/uthy-legacy-os --skill feature-ship-cycle
Clone the repo
git clone --depth 1 https://github.com/uthumany/uthy-legacy-os

Made for: Claude Code, Codex.

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.

agentmods badge for feature-ship-cycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/feature-ship-cycle/github.svg)](https://agentmods.dev/skills/uthumany/uthy-legacy-os/feature-ship-cycle)
Your own site
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/feature-ship-cycle"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/feature-ship-cycle/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.

agentmods 80×15 button for feature-ship-cycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/feature-ship-cycle"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/feature-ship-cycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 785 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00785
Opus 5.5 $0.00014 $0.00314
Sonnet 5.5 $0.00007 $0.00157
Haiku 4.5 $0.00003 $0.00078

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

Security

Grade A, and why

feature-ship-cycle 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 2mo 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.

workflows/feature-ship-cycle/SKILL.md · 74 lines

How it starts

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

Feature Ship Cycle (2-4 Weeks)

Overview

The feature ship cycle takes a validated concept from specification through development, launch, and post-launch evaluation. Use this when you've completed discovery and are ready to commit to building.

Instructions

This workflow runs across 2-4 weeks. Each phase must be completed before moving to the next. Handoff criteria at each gate prevent rework.

Phase 1: Spec (Week 1)

  1. Write the PRD — Load prd-writer skill. Include: problem statement, scope, requirements, success metrics, launch criteria
  2. Break down stories — Load epic-breakdown skill. Split the feature into sprint-sized stories
  3. Write acceptance criteria — Load acceptance-criteria skill. Given/When/Then for each story
  4. Update technical spec — Work with engineering on API contracts, data models, and architecture
  5. Design review — Hand off to design with clear scope

Output: PRD, user stories, acceptance criteria, design brief

Phase 2: Build (Week 2-3)

  1. Support engineering — Clarify requirements, answer questions, make scope decisions
  2. Review progress — Check demos, review designs, provide feedback
  3. Manage scope — If something is taking too long, negotiate scope reduction (not deadline extension)
  4. Update stakeholders — Weekly status updates using RAG framework

Output: Working feature in staging

Phase 3: Launch (Week 3-4)

  1. QA sign-off — All P0/P1 bugs fixed, acceptance criteria met
  2. Write release notes — Load release-notes skill. Write for end users and enterprise
  3. Prepare launch materials — Load go-to-market skill. Landing page, email, in-app messaging
  4. Plan rollout — Load rollout-strategy skill. Phased rollout with rollback criteria
  5. Go/no-go meeting — Review launch criteria, make the call

Output: Feature shipped, announcements live

Phase 4: Measure (Week 4+)

  1. Monitor metrics — Load metrics-framework skill. Track primary and counter-metrics
  2. Analyze results — Load experiment-analysis skill. Did we hit our targets?
  3. Gather feedback — Support tickets, user interviews, NPS
  4. Plan iteration — What to improve next? Load iteration-prioritization skill

Read the full file on GitHub · 74 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.

  1. 2mo ago First seen · 74 lines · 35 tokens per session scan A 6375653dfb35

Subscribe to this mod's changes

feature-ship-cycle is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 785 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.

Analytics and metricsProject management
Related

feature-ship-cycle compared with skills from other repositories

feature-ship-cycle next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
feature-ship-cycleuthumany/uthy-legacy-osSkill55mo agoMITA35Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex