Verify Spec

What it does

When your agent uses it

• Tasks that involve Accounting and bookkeeping

Example prompts

• “/verify-spec”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Bash(kubectl:*), Bash(flux:*), Grep, Glob

Workflow steps

7 steps, taken from the step headings in SKILL.md.

1. 1Locate inputs
2. 2Enumerate success criteria
3. 3Deploy the example (idempotent)
4. 4Watch reconciliation (Flux MCP)
5. 5Query observability (VictoriaMetrics / VictoriaLogs MCP)
6. 6Write the verification report
7. 7Summarize

What it can do on your machine

Read from SKILL.md and the folder at commit e5ee7e1. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Bash(kubectl:*)
  • Bash(flux:*)
  • Grep
  • Glob

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • kubectl

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use kubectl, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Spec loads about 1.5k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 483 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~65

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Smana/cloud-native-ref at commit e5ee7e1, republished under its Apache-2.0 licence (© Smana). 483 words, ~1,506 tokens.

name

verify-spec

description

Verify that a merged design's success criteria are actually met in the live cluster. Deploys the example manifest, watches Flux reconciliation, queries VictoriaMetrics/VictoriaLogs for evidence, writes docs/superpowers/specs/<topic>-verification.md.

allowed-tools

Read, Write, Bash(kubectl:*), Bash(flux:*), Grep, Glob

when_to_use

When the user says "verify the design", "did that actually ship", "check this works", "post-merge verification", "UAT this feature", "prove the success…

disable-model-invocation

true

argument-hint

<design-doc> — path to a docs/superpowers/specs/*-design.md file

paths

docs/superpowers/**

mcp__flux-operator-mcp__get_kubernetes_resources (kind: Kustomization/HelmRelease)
mcp__flux-operator-mcp__reconcile_flux_kustomization (if stalled)
mcp__flux-operator-mcp__get_flux_instance

# Verification: <spec title>

**Design**: <design-doc filename>
**Cluster**: <context>  (`kubectl config current-context`)
**Verified**: <YYYY-MM-DD HH:MM TZ>
**Verifier**: Claude (verify-spec)

---

## Success criteria results

| ID  | Criterion (1 line)                      | Method              | Verdict | Evidence |
|-----|------------------------------------------|---------------------|---------|----------|
| C-1 | Pods call AWS APIs without credentials  | kubectl exec probe  | ✅ PASS | `aws-cli output snippet` |
| C-2 | Evictions deterministic                  | VictoriaMetrics q   | ❌ FAIL | metric `cache_evictions_total` absent |
| C-3 | IAM roles cleaned up on delete           | kubectl delete + re-query | ✅ PASS | no dangling roles |
| C-4 | Reconcile < 2 min                        | flux get            | ✅ PASS | 42s |

## Issues found

### C-2 FAIL — eviction metric absent

<diagnosis, root cause hypothesis, suggested fix>

## Deployment artifacts

- Namespace: `<ns>`
- Flux Kustomizations: `<names>` — all Ready=True
- Helm releases: `<names>`
- Crossplane XRs: `<names>` — Synced=True, Ready=True

## References

- Design: `docs/superpowers/specs/<name>-design.md`
- Plan: `docs/superpowers/plans/<name>-plan.md` (if present)
- Example applied: `<path>`

© Smana, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/verify-spec of Smana/cloud-native-ref.

Open the folder on GitHubat commit e5ee7e1