create_feature_spec
writeFeature Specs
Create and save a feature specification.
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 | |
|---|---|---|---|
| domain | string | optional | Site domain |
| project_id | string | optional | Project UUID |
| title | string | required | Short, imperative title |
| description | string | optional | Full description (the what/why, not the how — use tasks for the how) |
| feature_type | enum("new_feature" | "enhancement" | "refactor" | "bug_fix" | "optimization" | "page" | "positioning") | optional | |
| priority | enum("critical" | "high" | "normal" | "low") | optional | |
| status | enum("idea" | "planned" | "in_progress" | "completed" | "verified" | "deprecated") | optional | Initial status. Defaults to 'planned'. Use 'idea' for captured-but-not-committed work. |
| tags | string[] | optional | |
| tech_stack | string[] | optional | |
| affected_files | string[] | optional | |
| ai_context_summary | string | optional | |
| next_action | string | optional | |
| tasks | object[] | optional | Implementation tasks. Break the spec into concrete steps. |
Related tools
get_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.create_spec_taskwriteAdd one or more tasks to a feature spec