Skip to content
Back to skills

Business Prepare Release

ASecurity

Prepare a reviewed business artifact for release, delivery, or human approval.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 7, 2026
ai-agents

Security analysis

A100/100

Scanned October 7, 2026

npx -y skills add greenfield-inc/agent-farm --skill business-prepare-release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Business Prepare Release?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Business Prepare Release
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-business-prepare-release-agent-farm/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-business-prepare-release-agent-farm)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: business-prepare-release
description: Prepare a reviewed business artifact for release, delivery, or human approval.
---

# Business release preparation

## Rules

- Run a fresh-context review independent of the artifact-stage review.
- Rewrite only where review identifies a concrete problem.
- Verify required patches and human approvals before marking the artifact ready.
- Preparation does not authorize sending or publishing.

## Read

Use supplied paths when present; the defaults are:

- `.business/artifacts/draft.md`
- `.business/reviews/artifact-review.md`
- `.business/artifacts/claim-evidence-ledger.md`
- `.business/specs/ready/spec.md`

## Fresh review

- Would a hostile or distracted recipient find the hole the earlier review missed?
- Does the core ask survive a 20-second skim?
- Is there any claim, number, or commitment we would be embarrassed to defend out loud?
- What did familiarity with this artifact make us stop noticing?
Send real problems back for correction before release.

## Write

- `.business/artifacts/final.md`
- `.business/reviews/release-checklist.md`

## Checklist

- reader and ask are obvious
- opening makes stakes clear
- no unsupported claims remain
- numbers/names/dates/pricing/commitments are consistent
- research-adversary objections addressed or intentionally excluded
- formatting/links/tables/screenshots work
- risks are named instead of hidden
- required human review is done or queued

Queued approval means blocked, not ready to release.

## Document handoff

- Read and update all artifacts in the supplied folder at the document destination your workspace instructions name, or that destination's default folder; pass this storage rule to reviewers and sync their outputs.
- Keep needed local files and privacy limits; without a destination, continue locally silently.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.