> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/service-patterns/3.-step-patterns.md). # 3. Step patterns Step patterns define a single user task within a user journey flow. They describe how the user completes that task on a page or screen. Step patterns are foused on user interactions and can be reused within functional patterns.
Cover image
Service catalogueServices catalogue (2).pngService catalogue
Service sheetService sheet.pngService sheet
Task listTask list (2).pngTask list
Before you startBefore you start page.pngBefore you start
Ask a questionQuestion page.pngAsk a question
Upload informationUpload documents (1).pngUpload information
Check answersCheck your answers.pngCheck answers
OutcomeOutcome page (1).pngOutcome
Ask for feedbackFeedback.pngAsk for feedback
Send a notificationChatGPT Image Feb 26 2026 from GovStack (1).pngSend a notification
MatchingChatGPT Image Feb 26 2026 from GovStack (2).pngMatching
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://specs.govstack.global/service-patterns/3.-step-patterns.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.