Skip to content
SpecifyDocs

First steps

Quickstart

Create your first document from GitHub, review the architecture, and share improvements with your coding agent.

Create your first document from a GitHub repository, review its architecture, and record improvements. Read generated results alongside the actual implementation.

Before you begin

  • A Specify account and workspace
  • A GitHub repository connected with permission for Specify to read it
  • Workspace administrator access to connect GitHub

See official pricing for available features and plans.

Create your first document

  1. Open your workspace home

    Sign in and select the workspace to use. Open Home in the sidebar.

    Workspace home with the action to create a document from a repository
  2. Choose a repository

    Select Create docs from GitHub. If this is your first connection, use Connect GitHub to choose which repositories Specify can access. Otherwise, the repository list appears.

    Selecting a connected GitHub repository
  3. Start document generation

    Select the repository and choose Create document. A request to read its default branch starts in chat. The English UI requests an English document.

  4. Inspect the saved result

    Follow progress in chat and open the generated document. Check its source paths, key features, and limitations against the repository. Continue in the same chat if there are errors or questions.

Continue with diagrams and improvement documents

Try this request in chat:

Create an architecture canvas showing the main components and call flow in this repository. Use the source paths in the document as evidence and list questions for connections that need further verification.

Read the diagram to identify differences from your intent, then record the evidence and desired behavior in an improvement document. Your coding agent can read it through MCP and update the actual code.

To update content when code changes, link each document and canvas to its repository. Using a repository during generation is separate from linking it for automatic updates. Automatic updates edit linked content directly, so inspect the edit history afterward.

Next steps