SuperAPI AI Directory

soia-dev-release-plan-checklist

General & other

View repository

Updated 10-16 08:46

About this skill

soia-dev-release-plan-checklist

Generate an executable, verifiable release checklist for internet software delivery. The input is the release scope and known constraints, and the output is a release plan with clearly identified items to be confirmed; it does not execute deployments, modify production environments, or replace release approval.

Scope: This skill handles software releases (code, service, client, or infrastructure delivery). Content publishing such as articles, social media, and videos is out of scope; please use the content publishing skill in the media domain.

Customer-Readable Description

What This Skill Can Do

Provide release goals, version/branch, environment, changes, and service dependencies; when information is incomplete, a draft with items to be confirmed can still be produced first.

Customer Wants Skill Will Do Customer Can See
Launch a software version Summarize version, branch, artifacts, configuration, and dependent services Phased release checklist and items with pending ownership
Control go-live risk Design testing, approval, rollback pre-check gates, and stop conditions Pre-check table with determinable pass/block status
Confirm results after canary Orchestrate canary scope, observation metrics, and verification steps Canary and post-release verification checklist

How Customers Use It

Describe the release goal in natural language, and provide as much as possible: service or product, target environment, version and source branch, artifact identifier, configuration changes, dependent services, expected window, approvers, and rollback plan. The following minimal input can be used:

release:
  product_or_service: <服务或产品>
  environment: <staging|production>
  version: <版本或提交标识>
  source_branch: <分支>
  artifact: <镜像、包或构建产物标识>
  config_changes: [<变更或无>]
  dependencies: [<依赖服务>]
  release_window: <时间窗口或待定>

Unknown information must be marked as "to be confirmed" and must not be guessed by the Agent as established fact. After the customer confirms the checklist, execute according to their existing release platform and permissions; this skill itself does not release.

Dependencies and Installation

This is a pure methodology skill with no hard dependencies, optional enhancements, or third-party tool dependencies, and no private configuration needs to be created.

claude plugin marketplace add soia-team/soia-open-skills
claude plugin install soia-dev@soia

When only this skill is needed, the npx route can be used. Note that the skill will land in the shared source of truth ~/.agents/skills; if a plugin is also installed, the same skill will appear in two indexes and each will drift, so it is recommended to choose one of the two:

npx skills add soia-team/soia-open-dev-skills -g -a '*' -s soia-dev-release-plan-checklist -y

The configuration convention uses schema v2; if the customer needs to save team defaults, the following files can be created on their own machine. If not created, work according to the input in the request:

~/.config/soia-skills/soia-dev-release-plan-checklist/config.yml

Do not record credentials, tokens, internal addresses, or real customer data in configurations or deliverables.

Workflow

  1. Confirm boundaries. Identify that this is a software release rather than content publishing; confirm the goal, environment, window, owner, and whether only a plan is to be generated. If the request is actually content publishing, explain that it should be transferred to the media domain and stop this process.
  2. Establish the release baseline. List the version, source branch or commit, artifacts and their sources, target environment, database or configuration changes, dependent services, and compatibility assumptions. Write missing items into the to-be-confirmed section.
  3. Generate pre-check gates. For each item, provide the responsible role, evidence, and blocking rules: build artifacts are traceable, automated/manual tests pass, change review and approval are complete, dependencies are healthy, capacity and monitoring are ready, and rollback artifacts and steps are available. Gates without evidence must not be marked as passed.
  4. Design release and canary. Define batches, coverage per batch, observation duration, core success metrics, error budget or stop thresholds, and the owners for pausing, rollback, and escalation according to the customer's release mechanism. If there are no thresholds, mark them as "To be confirmed"; do not fabricate values.
  5. Orchestration validation. Provide pre-release smoke checks, per-batch canary validation, full cutover confirmation, and post-release checks for functionality, performance, error rate, alerts, data integrity, and dependency chains. For each item, note the check method or evidence source.
  6. Review executability. Check whether versions, branches, artifacts, configurations, dependencies, approvals, and rollback correspond to one another; in particular, check the backward and forward compatibility of configuration/database changes and the feasibility of rollback.
  7. Deliver and retain decision points. Output the checklist, pre-check status, canary/validation steps, and open items. Only when the customer has explicitly authorized it and all relevant gates have passed may a move to the actual release process be recommended.

Output contract

The output is a Markdown release checklist and must include the following sections:

  1. Release summary: Scope, environment, window, version, branch, artifacts, owners, and the "software release" scope statement.
  2. Change and dependency checklist: Code/artifacts, configuration, data or migration, dependent services, compatibility, and items to be confirmed; each item has a status (known/to be confirmed/not applicable).
  3. Pre-check gates: Testing, approval, observability, dependency health, rollback plan, etc., listing responsible roles, evidence, pass conditions, and blocking conditions.
  4. Canary and release steps: Sequence, batches/scope, observation items, pass thresholds or values to be confirmed, stop/rollback actions, and owners.
  5. Post-release verification checklist: Smoke, business-critical paths, errors and latency, capacity, alerts, data consistency, dependent services, and customer feedback channels.
  6. Conclusion and open items: Conclusions that may proceed to the next stage, block release, or are for review only; items to be confirmed must not be described as passed.

By default, use fictional placeholders, for example <服务A>、<版本>、<制品标识>. When there is no actual evidence, output "unverified" and the next step to obtain evidence.

Private information and intermediate data

  • Use only the release information the customer actively provides in the current request; do not read company knowledge bases, private repositories, accounts, historical release records, or local private configurations to complete the checklist.
  • Do not request, record, or echo secrets, tokens, passwords, sessions, customer data, internal domains, or production access addresses. If the input contains such values, replace them with <已提供的敏感值>。
  • Intermediate information in the plan draft and reasoning is used only for the current session; if the customer requests it to be written to disk, they should choose a controlled location and retention period themselves and desensitize it first.

Logs and completion receipt

The final reply must provide:

  • Release elements covered (version, branch, artifacts, configuration, dependencies, testing, approval, rollback, canary, post-release verification);
  • The number of pre-check gate statuses (passed, blocked, to be confirmed) and the reason for each blocked or to-be-confirmed item;
  • Evidence used and items not actually verified;
  • Recommended next steps, such as completing artifact verification, confirming stop thresholds, or obtaining approval.

Do not say "checklist generated" as "already released" or "production environment verified".

Acceptance

Perform a forward check before delivery: select any gray-scale batch from the output and confirm that it simultaneously contains scope, observation items, pass conditions or pending confirmation markers, stop actions, and the responsible person; and confirm that every pre-check gate has evidence or a clear gap. If any item is missing, return to the corresponding process step to complete it.

WorkBuddy The loading unit of is role-based experts rather than plugins,npx skills add -a '*' cannot cover it, and it needs to be installed separately, see docs/install/workbuddy.md。