update_feature_spec
writeFeature Specs
Update spec body fields: title, description, status, priority, tags, etc..
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;
update_feature_spec is how your AI can reprioritize and retitle specs as plans change mid-discussion. 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 | optional | Rewrite the spec title |
| description | string | optional | Replace the spec description / body |
| feature_type | enum("new_feature" | "enhancement" | "refactor" | "bug_fix" | "optimization" | "page" | "positioning") | optional | Type of work this spec represents |
| priority | enum("critical" | "high" | "normal" | "low") | optional | Spec priority |
| status | enum("idea" | "planned" | "in_progress" | "completed" | "verified" | "deprecated") | optional | New spec status |
| next_action | string | optional | The immediate next step to take on this spec |
| tags | string[] | optional | Replace the tags array |
| tech_stack | string[] | optional | Replace the tech_stack array |
| affected_files | string[] | optional | Replace the affected_files array |
| ai_context_summary | string | optional | Short context summary for agents picking up the spec |
| assigned_to | string | null | optional | User the spec is assigned to; null clears it |
| depends_on_specs | string[] | optional | Spec UUIDs this spec depends on. Validated against existing specs. |