create_feature_spec
Generate structured feature specifications for Rampify projects by defining requirements, acceptance criteria, and implementation tasks from codebase context.
Instructions
Create and save a feature specification to Rampify.
IMPORTANT: Before calling this tool, YOU (Claude) must generate the complete structured spec from the user's description and your codebase context. Do not pass raw natural language — populate all fields:
Infer affected_files from open files and the codebase structure
Infer tech_stack from package.json and imports
Generate 3-5 acceptance criteria covering happy path, edge cases, and error handling
Break implementation into 3-8 concrete tasks with file references
Write ai_context_summary to help future AI agents understand the approach
Set next_action to the single most important first step
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Site domain (e.g., "example.com"). Uses SEO_CLIENT_DOMAIN env var if not provided. | |
| project_id | No | Project UUID — use instead of domain when no domain is configured. Accepts client ID (from /clients/[id]/ in the dashboard URL) or site UUID. Uses RAMPIFY_PROJECT_ID env var if not provided. | |
| title | Yes | Short, imperative title (e.g., "Add dark mode toggle") | |
| description | No | Full description of the feature, its purpose and user value | |
| feature_type | No | Type of feature (default: new_feature) | |
| priority | No | Priority level (default: normal) | |
| ai_context_summary | No | 2-3 sentence summary of architecture decisions for future AI agents | |
| next_action | No | The single next concrete step to start implementation | |
| tech_stack | No | Technologies involved (e.g., ["Next.js", "Tailwind CSS"]) | |
| affected_files | No | Files to create or modify (relative paths) | |
| tags | No | Categorization tags | |
| criteria | No | Acceptance criteria | |
| tasks | No | Ordered implementation tasks |