Our review
Makes the agent restate the target outcome, scope, non-goals, and acceptance criteria before any implementation code is written.
Strengths
- Surfaces product disagreements while changes are still cheap
- Leaves a written record of the decision before any scaffolding
- Explicit non-goals keep the scope from drifting
- The citable principle id makes it easy to point at why a decision changed
Limitations
- Purely conversational: no template or checklist for what good acceptance criteria look like
- Adds a round-trip that can feel heavy on trivial changes
- Assumes the user actually reviews the restatement; the agent cannot verify the framing is correct on its own
Use it when starting a feature, a refactor, or any material product change.
Skip it for narrowly scoped bug fixes or mechanical edits where the outcome is already unambiguous.
Security analysis
SafeThe skill is a process guideline that instructs the AI to define outcomes, scope, and acceptance criteria before generating implementation. It declares no tools and contains no executable commands, network calls, or destructive actions. There is no meaningful execution risk.
No concerns found
Examples
I want to add team invitations to our app. Before writing any code, restate the outcome, scope, non-goals, and acceptance criteria, then wait for my confirmation.We're about to refactor the billing module. Think before typing: what is the target outcome, what is explicitly out of scope, and how will we know it's done?Users say onboarding is confusing. Don't scaffold anything yet — write the decision first: outcome, boundaries, and acceptance criteria.name: "thinking-before-typing" description: "Define outcome, evidence, and boundaries before generating implementation." disable-model-invocation: false
<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->thinking-before-typing
Restate the user outcome, scope, non-goals, and acceptance criteria first. Code comes after the decision is visible.
When: Starting a feature, refactor, or any material product change.
Why: Generation speed makes unexamined ideas look finished. Writing exposes disagreement while change is cheap.
Do not: Open with a scaffold or rewrite when the outcome is still conversational.
Cite this principle by id when it changed a decision. Keep the citation specific.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.