Specs
Specs turns SEO findings into work your AI coding tool can actually implement. Every improvement becomes a feature specification, with tasks, acceptance criteria, and a commit trail, instead of a bullet in a report nobody executes.
One list of everything to build#
Every piece of work is a spec, whoever builds it. Rampify files specs for what a scan finds, your AI tool files them as you work, and you can write one with New Spec. The list groups them by where they stand:
| Status | What it means |
|---|---|
| Idea | A proposal waiting on your yes or no |
| Planned | Approved and ready to hand out |
| In progress | Someone is building it: you, your AI tool, or the Rampify agent |
| Done | Built, not live yet |
| Live | Live on your site |
| Not doing | Set aside, kept with its reason |
Open (Ideas, In progress and Planned) is the default view. Filter by goal, type, who is doing it, or a search, and sort by priority, by what was worked on most recently, or by newest. The filters stay in the address, so a link shows the same list. Switch to the board for a column per status.
Decide on Ideas#
Ideas sit at the top because they need you. Each one says why it's worth doing. Approve makes it a planned spec; Reject sets it aside, with an optional reason that's kept as a lesson. A rejected Idea can be restored later.
Hand a spec to your AI tool#
The point of a spec is that you don't implement it by hand. Start on a planned spec copies a prompt for your AI tool, which pulls the spec over MCP and works it task by task. A spec moves to In progress, and shows who is doing it, when the work actually starts, not when you copy the prompt.
The prompt carries the spec and the project, so your AI tool has everything it needs.
The AI fetches the spec with get_feature_spec and sees the same tasks and criteria you do.
As the AI marks tasks complete and links commits, the spec moves along, with no copy-paste status updates.
Work toward goals#
A goal is what your project is working on now, with a number Rampify measures: pages indexed, search clicks, conversions. You can have up to 3 at once. They show in the top bar on every page, and Rampify suggests goals that fit your launch phase. A spec can serve a goal; filter the list by a goal to see the work behind it.
Big pieces of work and their parts#
A spec can be part of a bigger one. The bigger spec's row shows how far along its parts are, and each part says what it belongs to. Open the bigger spec to see every part and where it stands. Your AI tool links them when it files the parts.
Trace specs to commits#
Tasks and acceptance criteria live on the spec; commits link back to both. A commit that did several tasks, like a squash merge, is linked to each of them. Your AI can generate a conventional-commits message straight from spec context, so six months later git log still explains why a change happened.
From your AI tool
Everything above is also reachable over MCP: same data, no dashboard tab. The toolbar's MCP handoff on this page pre-fills the project context for you.