SF ShipGlows
Menu Open navigation menu Close navigation menu
Audit & Improve Featured

Skill Detail

sg-verify

Check whether the work really satisfies the user story, not just whether the code compiles.

A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.

Problem

What problem this solves

Technical checks can pass while the work still misses the actual promise, leaves docs stale, or hides risky edge cases.

Outcome

What changes when it works

You get a more honest readiness call before the changes move into closure or release, with open bug records folded into the decision when relevant.

Why It Matters

What this changes for a solo founder

This skill matters because finished code is not the same thing as finished work. It asks whether the outcome is actually safe, complete, maintainable, and proven enough to trust, including whether unresolved bugs still block the story.

When to use it

  • After implementation is done
  • When the task touched meaningful behavior, data, or user-facing outcomes
  • Before closing a task or shipping changes
  • After standard verification when you want to challenge materially average choices

What you give it

  • A completed implementation or review target
  • The current task contract or user story when available

What you get back

  • A behavior-aware readiness judgment
  • Findings around completeness, risk, and regressions
  • A decision-quality check for correctness, security, relevant performance, maintainability, and proof
  • A verification result in the spec's chantier flow when a unique spec is in scope
  • A callout for linked open bug records when they affect the scope
  • A route to sg-browser when non-auth browser evidence is missing
  • Validation of project-aware editorial scores when a spec or workflow declares a content quality gate
  • A stronger basis for end-of-task or shipping decisions
  • A standard verified verdict without implying excellence
  • A verified_with_excellence_gaps or excellent verdict after mode=excellence or an unambiguous natural-language excellence request

Typical examples

  • /sg-verify
  • /sg-verify after onboarding fix
  • /sg-verify current branch before ship
  • /sg-verify vérifier le gate de score éditorial
  • /sg-verify mode=excellence current verified work

Limits

  • It raises the quality bar, but cannot prove the absence of every defect
  • Weak upstream specs still reduce the strength of downstream verification
  • Open linked bugs remain part of the verification verdict when they touch the scope
  • Excellence mode does not replace a specialist audit for design, copy, security, performance, or architecture

Related Skills

See the rest of the loop around this move.

Build & Fix

sg-browser

Open a URL in a real browser and verify one observable non-auth objective.

A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.

Open skill page
Operate & Ship

sg-check

Run the standard technical checks and fix the obvious issues before you pretend the work is done.

A practical quality gate for typecheck, lint, build, and related technical validation in the current project.

Open skill page
Operate & Ship

sg-end

Close a task cleanly so the work is summarized, tracked, and ready for the next thread.

A task-closing skill for wrapping up implementation, documenting completion, and recording closure in the chantier flow when applicable.

Open skill page
Operate & Ship

sg-ship

Commit and push quickly when the work is actually ready, instead of stretching closure into another vague step.

A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.