Product workflow3 min readKeep one real product question in mind as you read.

A useful way through

Start with one real question and leave with a next step.

Start with the question in front of you, then use the guide to make the next decision easier.

Try saying

“I am trying to make this decision. What should I look at first?”

Start with context

Bring the smallest useful example.

Look for the signal

Separate what is known from what is assumed.

Take one step

Choose an action you can review.

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. Specky opens the GitHub App installation flow when the App is configured; OAuth is an explicit fallback for development or an existing OAuth connection.
Install the Specky GitHub App on your GitHub organization or personal account (requires the appropriate GitHub permission)
Select which repositories Specky may use, then choose a default repository and branch for repo-native actions such as validation pages
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

The App connection uses short-lived installation tokens and the repository scope you approved. Specky does not store a long-lived App installation token. The selected repository and default branch are workspace settings, so chat, MCP, integrations, and validation-page delivery resolve the same destination instead of each keeping a separate repo choice.

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.space/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

Ready to apply this?

Start with your own product and keep the first read grounded. You can create an account after you see the result.

Try the guided start