fast_specLABSCO SUMMARY
A spec tool with a browser attached is the combination that matters — most specs fail on unresearched assumptions.
The gap between a bad spec and a good one is rarely writing quality; it is whether anyone checked how the thing being integrated with actually works. Giving the architect its own browsing tool means those checks can happen inside the same pass rather than being left as open questions for whoever implements. Start with fast_spec to see whether the shape is right before spending a deep run on it.
What it is
Pre.dev's architect agent, reachable as a hosted endpoint. It sits before the code: you describe what you want built and it produces the specification.
What you get
- fast_spec — a quick specification pass
- deep_spec — the thorough version
- browser_agent — browse for the context the spec needs
Requirements
OAuth with PKCE and dynamic registration against api.pre.dev, or an API key header. A credit-based subscription funds the runs.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Sketching the shape
A quick pass to see whether the direction is right before spending more.
02
The real specification
The thorough run, once the shape is settled.
03
Checking an assumption
Browse for the context the spec depends on.
3 tools
Listed in project docs. Your client may show a different list.
deep_specbrowser_agentBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 authorization code with PKCE and dynamic client registration, or a predev-api-key header
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.pre.dev/mcpRequirements
- OAuth 2.0 authorization code with PKCE and dynamic client registration, or a predev-api-key header
