ai-team-library/claude/skills/release-notes/SKILL.md
# Skill: Release Notes ## Description Collects completed work items, merged changes, and resolved issues from a release cycle and produces structured release notes, a changelog entry, and a known issues list. The skill reads task completion records, PR summaries, and the generation manifest to build a comprehensive picture of what changed, then formats it for both technical and non-technical audiences. This supports the DevOps/Release Engineer and Technical Writer personas. ## Trigger - Invo
npx skillsauth add beekeeper-lab/foundry ai-team-library/claude/skills/release-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Collects completed work items, merged changes, and resolved issues from a release cycle and produces structured release notes, a changelog entry, and a known issues list. The skill reads task completion records, PR summaries, and the generation manifest to build a comprehensive picture of what changed, then formats it for both technical and non-technical audiences. This supports the DevOps/Release Engineer and Technical Writer personas.
/release-notes slash command.| Input | Type | Required | Description |
|-------|------|----------|-------------|
| version | String | Yes | Version identifier for this release (e.g., "1.2.0", "2025-Q1-sprint-3") |
| tasks_dir | Directory path | No | Directory of completed tasks; defaults to ai/tasks/ |
| previous_version | String | No | Previous version for comparison; used to scope what's "new" |
| changelog_file | File path | No | Existing changelog to append to; defaults to CHANGELOG.md |
| audience | Enum: internal, external, both | No | Who the notes are for; defaults to both |
external, focus on user-facing changes and omit internal refactoring. If internal, include technical details and infrastructure changes. If both, produce both variants.| Output | Type | Description | |--------|------|-------------| | release_notes | Markdown file | Full release notes document for the version | | changelog_entry | Text (appended) | Entry appended to the existing changelog file | | known_issues | Section in notes | List of open issues and limitations shipping with this version |
| Error | Cause | Resolution |
|-------|-------|------------|
| NoVersionProvided | Version identifier not supplied | Provide a version string |
| NoCompletedTasks | No tasks marked complete in the specified range | Verify task status or broaden the version range |
| ChangelogNotFound | Changelog file path does not exist | Create a CHANGELOG.md or specify the correct path |
| GitHistoryUnavailable | Not a git repo or git not installed | Release notes will be built from tasks only, without PR data |
development
# Skill: VDD (Verification-Driven Development) Gate ## Description Runs the programmatic VDD gate for a bean: parses the bean's `## Acceptance Criteria` section, dispatches each criterion's evidence type to the matching runner (test, lint, file, file-contains, or manual), aggregates the results into a pass/fail verdict, and writes a structured markdown report at `ai/outputs/tech-qa/vdd-<NNN>.md` (zero-padded NNN). This is the machine-checkable counterpart to the prose VDD policy in `ai/contex
tools
# Skill: Spawn Task ## Description Dispatches a single specialist persona to execute a single task with only that task's context. Auto-detects the runtime environment and chooses one of two execution paths: - **In tmux** (`$TMUX` set): spawn a worker in a git worktree using a child tmux window. Process-isolated, parallelizable, durable across the calling session's lifetime. Same pattern as `/spawn-bean` but at task granularity. - **Not in tmux**: invoke the `Agent` tool with `subagent_typ
development
# Skill: Orchestration Report ## Description Aggregates the per-bean **Orchestration Telemetry** blocks (BEAN-278) across recent Done beans and produces a markdown report that answers the architecture-aware-evaluation question: **is the orchestration paying for itself?** Distinct from `/telemetry-report` (which aggregates raw cost, duration, and tokens); this skill aggregates the orchestration-quality metrics layered on top — bounces, persona activations, contract violations, escape-hatch usag
development
# Skill: Health Check ## Description Runs all health checks defined in `ai/context/health-checks.md` and produces a table-format report. Can be called standalone or by other skills (e.g., `/long-run`). ## Trigger - Invoked by the `/health-check` slash command. - Called programmatically by `/long-run` at the start of each cycle. ## Inputs | Input | Type | Required | Description | |-------|------|----------|-------------| | health_checks | Markdown file | Yes | `ai/context/health-checks.md`