Task: specification and projects
Check requirements and the deliverable location.
Use the fictional Aurora Page example in a test project. For assistant requests, write in the indicated lead or worker chat. Perform the remaining steps in the panel.
Steps
Open Specification and read requirements and acceptance criteria. Compare them with the card’s short description.
Under Projects, check name and path. Use folder or editor actions only when the local environment advertises support.
Under Repositories, open the available web link. If a project or repository is unidentified, ask the lead for the correct information.
Record that Aurora needs a heading, description and contact button in the specification. Confirm the actual test-project path.Check the result
The specification holds requirements. A project can exist without a Git repository. Local paths open only on a machine with access to that folder.
When the specification includes a diagram, inspect its visualization and source-code option. A rendering error leaves the source text available.
Local actions are Open in Explorer and Open in VS Code. They require an existing folder and local-opening support from the service. An error appears beside the controls. Without linked scope, the section reports that scope was not provided.
If the record is missing, clear the section’s filters, check active or archived registration where that control exists, and confirm the correct team, board or task. A connection failure appears as an error and requires a retry.
Open the example screen
Copy the record address from your own panel. Preserve its slug and change only the tab parameters as shown below. The example path describes navigation and needs your actual record.
/app/tasks/<slug>?tab=specificationPaste the address copied from the open task. The link below changes only the tab and preserves your service address.
Continue with the next chapter or consult the index. Usage guide index