Streamline your technical peer reviews with Attain OS Forms. Use the Architecture Review Request form, drafted by Atty AI, to submit specs for feedback.
Every engineering team hits that moment when a design decision needs a second pair of eyes. You’ve sketched out a microservices breakdown, chosen a database, or drafted an API contract—but before it goes live, you need a formal architecture review. The problem? Chasing down reviewers, formatting context, and keeping the feedback loop organized. Attain OS Forms cuts that friction with a dedicated Architecture Review Request form, and its AI agent Atty drafts the submission for you.
Instead of stitching together a document from email threads, Slack messages, and a shared doc, you get a single, structured form that captures the architecture’s purpose, scope, risks, and open questions. Atty pulls from your project context (tasks, notes, documents) to pre-fill the request. You review, tweak, and publish—your peers see a clean summary, not a wall of text.
Your team is proposing a new payment-processing microservice. You need to explain the async event flow, the chosen message broker, and how it handles retries. Instead of writing a multi-page doc, you open the Architecture Review Request form, and Atty drafts the technical summary from your existing Notes and Documents. You add the context diagram reference and submit. Reviewers see exactly what they need to evaluate.
You’re migrating a legacy monolith’s customer table to a normalized schema. The change affects three other services. You fill out the form with the current schema, target schema, and migration plan. Atty automatically includes links to related Tasks (like “update reporting queries”) and a risk assessment. The review board gets a focused request without hunting for background.
You’re adding a new endpoint to an existing REST API. The change needs approval because it breaks backward compatibility. You submit a review request with the OpenAPI spec snippet, the rationale, and a list of affected clients. Atty drafts the “impact analysis” section from your project’s Notes on client dependencies. The form ensures no detail is missed.
Navigate to Forms in Attain OS and select the Architecture Review Request template. The form is pre-configured with fields for title, architecture type, context, design decisions, risks, and open questions. Atty already knows your project from your active workspace.
As you open the form, Atty scans your recent Notes, Documents, and Tasks related to the architecture topic. It generates a draft for the “Context & Background” and “Design Decisions” fields, including references to relevant files. You see a nearly complete submission—no blank page syndrome.
Read Atty’s draft. Maybe you need to adjust the risk level or add a diagram reference. Update the form fields directly—add a date for the review meeting, select the architecture type (e.g., “Microservices”), and check the required reviewers. The form keeps everything in one place.
Click Submit. Attain OS records the request in your project’s Backlog and sends a notification to the assigned reviewers via The Feed and email (if configured). Reviewers see a structured request with all context inline. No more “where’s the design doc?” emails.
A close-to-finished draft — not a blank page. Here's the kind of result the flow hands you, ready to review, tweak, and publish.
Submit your technical architecture for peer review. Provide context, design decisions, and open questions so reviewers can give focused feedback.
The request is saved in your project’s Backlog as a ticket. Assigned reviewers are notified via The Feed and (if configured) email. They can view the full form details and leave comments on the ticket. There’s no automatic syncing with external tools—everything stays inside Attain OS.
Yes. When you open the form, Atty scans your current project’s Notes, Documents, and Tasks to draft the Context & Background and Design Decisions fields. It pulls relevant text and links. You should always review and edit the draft before submitting.
The form does not include a reviewer assignment field or calendar integration. Instead, after submission, you can manually assign the ticket to team members using the Backlog app. For scheduling, use the separate Calendar app to set a review meeting. The form is purely for capturing the architecture details.
Attain OS does not have a template duplication feature. However, you can open a previous submission in the Tickets app, copy its content, and paste it into a new form. Alternatively, save a Note with your standard architecture review structure and refer to it each time.
