sg-ready

Pressure-test a spec before implementation so the thread is not coding against loose intent.

A readiness gate for checking whether a spec is complete, safe, and executable by a fresh agent.

Browse skills on GitHub Back to the hub

Problem

What problem this solves

Many specs look fine until implementation begins and missing assumptions start turning into guesses.

Outcome

What changes when it works

You get a clearer signal on whether the spec is ready to code or still too weak to trust.

Why It Matters

What this changes for a solo founder

This skill helps you spend structure where it pays off. It catches vague contracts before they become expensive implementation drift.

When to use it

After writing a non-trivial spec
Before handing a task to implementation
When scope, security, or edge cases may still be underspecified

What you give it

A draft spec
The current repo and decision-doc context if needed

What you get back

A readiness judgment
Findings on missing assumptions or vague tasking
A safer handoff into implementation

Typical examples

/sg-ready pricing page rollout
/sg-ready auth rewrite spec
/sg-ready current spec

Limits

It validates the contract, not the final implementation
A ready spec still needs disciplined execution and verification later

Related Skills

See the rest of the loop around this move.

Plan & Decide

sg-spec

Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.

The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.

Open skill page

Build & Fix

sg-start

Start implementation when the task is ready, and force a stronger path when it is not.

The main execution entrypoint for beginning real work after the problem and contract are clear enough, while keeping the chantier flow visible.

Open skill page

Audit & Improve

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.

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.

Documentation Overview Open skills on GitHub Return to the skills hub