MCP Tools/Feature Specs/create_feature_spec

create_feature_spec

writeFeature Specs

Create and save a feature specification.

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_feature_spec is how your AI can file work the moment a finding surfaces, before it's forgotten. 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

ParameterTypeDescription
domainstringoptionalSite domain
project_idstringoptionalProject UUID
titlestringrequiredShort, imperative title
descriptionstringoptionalFull description (the what/why, not the how — use tasks for the how)
feature_typeenum("new_feature" | "enhancement" | "refactor" | "bug_fix" | "optimization" | "page" | "positioning")optionalType of work this spec represents
priorityenum("critical" | "high" | "normal" | "low")optionalSpec priority
statusenum("idea" | "planned" | "in_progress" | "completed" | "verified" | "deprecated")optionalInitial status. Defaults to 'planned'. Use 'idea' for captured-but-not-committed work.
tagsstring[]optionalFreeform tags for grouping and filtering specs
tech_stackstring[]optionalTechnologies involved in the work
affected_filesstring[]optionalFiles expected to change
ai_context_summarystringoptionalShort context summary for agents picking up the spec
next_actionstringoptionalThe immediate next step to take on this spec
tasksobject[]optionalImplementation tasks. Break the spec into concrete steps.