First steps
Understand and review code through diagrams and feature documentation. Start with visualization, certification documents, or MCP.
Specify is a workspace that turns code into diagrams and plain-language feature documentation. Understand what your coding agent built, review where it differs from your intent, and record improvements in documents your agent can read.
Start with the result you need
Understand and review code through diagrams
Ask for architecture, feature flows, and API behavior grounded in the repository, then read the results. Compare the structure and behavior with your intended design and requirements.


- Understand — Connect a repository and create a project overview and behavior documentation.
- Review — Read documents and canvases to check dependency directions and feature flows against requirements.
- Improve — Use chat to record improvements in a document your coding agent can read through MCP.
- Check again — After the next change, inspect updates to documents and canvases linked to the repository.
Prepare certification documents
Certification documents start from the same evidence. Collect product overviews, requirements, designs, and test material; distinguish confirmed facts from missing evidence when drafting. The certification document guide explains what to prepare and review.
See Specify Certify for supported areas and expert review needs. Complete submission material through expert review, and establish certification and conformity through the applicable assessment process.
Give your agent the same context
Let your coding agent find and read the improvement document directly. Connect Specify MCP and ask your coding agent: “Read the improvement document in Specify and update the implementation accordingly.” See MCP tools for search, reading, and permitted writing tools.