Documentation automation
Read a repository to create feature documents and architecture canvases, then check their evidence.
Specify reads GitHub code to create feature documents and architecture canvases. Connect repositories to the resulting content to keep it aligned with later changes. Create the outputs you need, then enable updates for each one.
Before you start
Connect GitHub and confirm that the app can access the repository. Choose the workspace and folder where the results should be saved.
Create your first document and canvas
- Select the repository in chat or mention it with
@. - Describe the feature, audience, and output format. Start with a key flow and expand to the scope you need.
- When the agent has inspected the code and saved a document or canvas, open the result. Answer any follow-up questions in the same conversation.
Check the login flow in this repository against the code.
Create a document covering entry points, authentication, storage,
and error handling, plus an architecture canvas showing component relationships.
Mark anything you could not verify separately.

Check the saved results
Compare document claims with the source code. For canvases, check components, connection directions, and external dependencies. After the run completes, review the saved content and request any missing details in the same conversation.


Connect automatic updates
In each document or canvas, open Connections → Manage connections → Event connections and check the repository. Starting with the next push to the linked default branch, Specify analyzes changes and directly updates that content. Connect both outputs if you want both to stay current.


Expand your documentation
Request API explanations, onboarding guides, and operating procedures from the same repository, then organize them into folders. Manage reusable writing instructions as skills. After updates, check the results.