AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Definition Of Done

skill-vincentchuwaichow-vanguard-frontier-agentic-definition-of-done · by VincentChuWaiChow

The ordered finish-line runner for any change in this repo — generators, then the asset-integrity refresh last on its own, then the full gate suite, then commit and push; use before declaring any change finished or whenever the stop hook reports uncommitted or untracked changes.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-vincentchuwaichow-vanguard-frontier-agentic-definition-of-done

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-vincentchuwaichow-vanguard-frontier-agentic-definition-of-done)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
13d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Definition Of Done? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Definition of Done

Doctrine

The order is load-bearing. The integrity manifest must hash the settled tree, so asset-integrity:write always runs last, on its own, from the repo root — never folded into a parallel generator batch, never run from a subdirectory.

Trigger

  • Before declaring any change in this repo finished.
  • Whenever the stop hook reports uncommitted or untracked changes.

Input

The list of paths you touched in this change.

Decision matrix

Pick the steps that apply based on what changed — most changes trigger more than one row.

  • catalog / agents / skills / roles / providers changednpm run manifest:write:all,

then re-run asset-integrity LAST on its own (the parallel-generator ordering caveat in CLAUDE.md).

  • skills/** changednpm run manifest:write.
  • catalog/model-policy.json or model-registry.json changed → `npm run

model-policy:check (and model-policy:apply` if the projection changed).

  • tools/vfa-tui/** changed → `cd tools/vfa-tui && cargo fmt --check && cargo clippy

--all-targets -- -D warnings && cargo test. Return to the repo root afterwards — a persisted cd` has broken integrity runs before.

  • any root file / agents/ / plugins/ / package.json changed → asset-integrity

refresh required.

The invariant sequence

Always, in this order:

  1. Applicable generators from the decision matrix above.
  2. python3 tests/validate-asset-integrity.py --write from the REPO ROOT, last, on its own.
  3. npm run validate — zero failures.
  4. npm run lint:spell and npx --yes markdownlint-cli2 "**/*.md" "#node_modules" — zero

failures.

  1. git status clean after committing with a scoped conventional-commit message.
  2. git push -u origin (retry with backoff on network errors only).

Footguns

  • grep -cE 'FAIL|ERROR' exits 1 on a count of 0 — do not chain it with && before the

commit, or a clean gate run looks like a failure and blocks you.

  • Run integrity from the repo root — a leftover cd into tools/vfa-tui makes the write

silently target a nonexistent path.

  • Warnings from model-policy are exit-0 by design — read them, don't treat them as failures.
  • Never edit catalog/asset-integrity.json by hand.

Output

The checklist above with pass evidence per step, then the commit hash and push confirmation.

Delegation note

Gate runs may be delegated to a Haiku subagent per agentic-delegation's "Gate run" workflow template, but the orchestrator reads the results and owns the commit — a delegate's self-report that gates passed is not verification.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.