SpeckyDocs

GitHub Integration

What it does

The GitHub integration pulls engineering activity — pull requests, issues, and optionally commit messages — into Specky as signals. This gives you visibility into what's actually being built and shipped, and lets you connect engineering work back to product decisions and PRDs.

GitHub signals are particularly useful for:

  • Seeing which features are actively being worked on
  • Identifying technical debt signals from issue labels and PR descriptions
  • Tracing shipped work back to the PRD that motivated it
  • Catching scope creep when PRs reference requirements that weren't in the original spec

    • When to use it

  • To see engineering work alongside customer feedback in the Discovery Hub
  • To link GitHub PRs to Specky PRDs for traceability
  • To surface technical debt and engineering risk signals in Risk Radar
  • To track which roadmap initiatives have active engineering work

    • Setup

  • Go to Settings → Integrations → GitHub
  • Click Connect GitHub
  • Install the Specky GitHub App on your GitHub organization (requires org admin)
  • Select which repositories to sync
  • Configure sync options:
    • - Issues: on by default - Pull requests: on by default - Commit messages: off by default (enable for additional signal coverage)
  • Click Start Sync

    • What gets synced

  • Pull requests: title, description, comments, review comments, status (open/merged/closed), linked issues
  • Issues: title, description, comments, labels, status, assignees
  • Commit messages (if enabled): commit title and body from merged PRs

    • What is NOT synced:

  • Code content — Specky never reads your source code
  • Private repository data unless you explicitly grant access during setup

    • Linking PRs to PRDs

    When a PR description includes a Specky PRD link (e.g. Implements: https://app.specky.io/docs/prd-123), Specky automatically links the PR to that PRD. You can then see all PRs implementing a given PRD from the PRD Editor's Activity panel.

    Tips

  • Add a PR template to your repos that includes a "Specky PRD" field to encourage linking
  • Use GitHub issue labels like customer-reported or feature-request to improve signal classification
  • Enable commit message sync for repos where engineers write detailed commit messages