create_spec_criterion
writeFeature Specs
Add an acceptance criterion to a feature spec.
Connected surface
This tool and the Specs dashboard page are two surfaces over the same data. The dashboard is where you view and curate it;
create_spec_criterion is how your AI can pin down what “done” means while it's being negotiated. How surfaces connect →Write tool
Mutates Rampify state, triggers background work, or calls a paid external API. Most clients ask for confirmation before invoking.
Parameters
| Parameter | Type | Description | |
|---|---|---|---|
| spec_id | string | required | Spec UUID |
| title | string | required | Criterion title |
| description | string | optional | What the criterion verifies |
| criterion_type | enum("functional" | "technical" | "performance" | "security" | "accessibility") | optional | Default 'functional' |
| verification_method | enum("automated_test" | "manual_qa" | "code_review") | optional | Default 'manual_qa' |
| status | enum("pending" | "implemented" | "tested" | "verified") | optional | Criterion status; default 'pending' |
Related tools
create_feature_specwriteCreate and save a feature specificationget_feature_specreadFetch one spec by UUID with full nested detaillist_feature_specsreadFind specs by search/status/priority/tags/etc; supports summary_only for fast scansupdate_feature_specwriteUpdate spec body fields: title, description, status, priority, tags, etc.