agentleFS
20030419zhanghongyi20030419zhanghongyi/AI-Software-Engineering-Workflow-Template/.agents/skills/launch-check/SKILL.md

launch-check

Skill0 starsChanged 6 months agoMITView on GitHub

Check launch readiness before release decisions.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read the files above.

    line 39
  2. Distinctive:

    Check that the task is in Launch Gate.

    line 40
  3. Distinctive:

    Do not automatically commit, push, merge, release, tag, or force-push unless the user explicitly approves that exact action.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch Check

Purpose

Generate a Launch Review Artifact for Launch Gate.

When to use

  • A release decision is coming
  • Metrics or feedback channels must be checked
  • The user wants a beta or release recommendation

Required files to read

  • AI_WORKFLOW.md
  • docs/11_stage_gates.md
  • docs/13_human_gate_and_rollback.md
  • .ai/artifacts/LAUNCH_REVIEW_ARTIFACT_TEMPLATE.md

Inputs

  • Review Artifact
  • Release goal
  • Target users
  • Metrics and feedback plan

Outputs

  • Launch Review Artifact
  • Decision suggestion: release / private beta / delay / rollback

Steps

  1. Read the files above.
  2. Check that the task is in Launch Gate.
  3. Review release goal, target users, metrics, feedback channels, and rollback plan.
  4. Generate the Launch Review Artifact.
  5. Require Human Owner review and stop.

Human review

Human Owner must review the artifact and choose release, private beta, delay, or rollback.

Stop conditions

  • Release goal is unclear
  • Metrics are missing
  • Feedback channels are missing
  • Rollback plan is missing
  • User has not approved the decision step
  • There is any automatic commit / push / merge / release risk

Codex safety rule

Do not automatically commit, push, merge, release, tag, or force-push unless the user explicitly approves that exact action.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.