Specify

Use when a feature, change, or product idea is still fuzzy and must become an approved WHAT/WHY spec before any planning or code — the brainstorming front door of ASDD stage 2 (Spec). Turns a one-line intent into problem, goals, users, out-of-scope, the four ASDD questions (what the user can do, what result they get, what it must respect, how it proves it) and acceptance criteria, via frontier-round dialogue and 2-3 approaches with a recommendation, carrying zero implementation detail. Fires whenever someone jumps to HOW before WHAT is agreed, in any language. NOT the technical plan (that is `plan`), NOT the de-risking ambiguity sweep (that is `clarify`), NOT project-wide principles (that is `constitution`).

ericrisco Updated 610 repo stars
rsc-harness: you build the product, rsc-harness builds your agent's harness, following strict best practices instead of improvising one.

File contents

ericrisco/rsc-harness commit 97b82e52ff

Frequently asked questions

npx get-skill add ericrisco/specify