Skip to content
SpecifyDocs

Workflows

Find a workflow for your work

Choose a planning, development, customer, or quality problem and find the sources, Specify workflow, and results for solving it.

Are developers working from old requirements? Is evidence for customer answers hard to find, or does documentation disagree with code? Choose the case closest to your current problem to see what to prepare, do in Specify, and review.

Choose by the problem you face

Each guide starts with a problem and shows the Specify workflow and resulting documents. Begin with an example or a small document, then use the same workflow with your team’s sources.

Plans change, but development uses an old copy
Keep requirements in a shared Specify document and reread it through MCP in Claude Code or Codex. Align changed conditions with implementation plans and tests.
For planners, PMs, and developersYou cannot tell which security answer is current
Compare current policies with past responses to prepare answers, evidence, and review status. Gather questions that need an owner’s confirmation.
For sales and security teamsOwnership changes, but implementation scope is unclear
Compare project notes with code to separate implemented features from unfinished requests. Leave run instructions and the next owner’s checklist.
For development and maintenance teamsRelease communications disagree with the FAQ
Prepare an announcement and FAQ update from change notes and existing answers. Align changed explanations with limits and conditions that remain.
For PM, support, and marketingGaps in medical device development documents are hard to find
Create code-backed requirements, design, and SOUP drafts plus a gap report. Owners and experts review omissions and unconfirmed items.
For development, regulatory, and quality teamsAPI code changes while docs and examples stay behind
Connect GitHub changes to evidence-backed documentation updates. Compare requests, responses, and examples across related documents before applying them.
For API development teamsNew teammates get stuck before their first run
Use the repository to draft setup, run, and code-reading instructions. Add team procedures and improve the guide by following it in a clean environment.
For new teammates and development teams

Review every draft the same way

  1. Set the scope. Name the source files, product version, time period, and repository commit.
  2. Check the original evidence. Open source material instead of relying on search snippets. If a source does not appear, check indexing and access.
  3. Ask for a reviewable format. Request a table, comparison, announcement, or checklist with source IDs, review status, and unresolved items.
  4. Compare the draft with the sources. Separate facts from suggestions. Keep items that need an owner unconfirmed until someone verifies them.
Connecting a service does not automatically index every external item. Check knowledge search scope and each connector's read scope. When reusing a generated answer, check its original evidence and date.

Practice with the sample materials

The questionnaire, handover, and customer-update examples share the RelayDesk Demo material pack. It contains fictional policies, an older FAQ, change notes, and a fixed code copy so you can compare differences between sources. It contains no real customer information or actual Specify security policies.

Each guide includes screens from actual source-grounded app execution, example requests, and human review checks. The medical device guide provides its own separate code example.