Build kit / Operations

Change-order control

Submit scope changes, route them for approval, and record the resulting work.

Your app idea

Describe the
app you want.

Tell your agent what you want the app to do. You can work through the details together. This page does not save your changes.

The business or clientWhat the app should doSoftware you use & tools you build with

Use a summary of the business. Keep credentials and sensitive client records out of prompts.

The maintained Swirls agent instructions

Help me design and build: Change-order control.

Intended outcome: An application for submitting, reviewing, approving, and tracking change orders.
Business / client: [Describe the business or client]
Process and requirements: [Describe the process, people, rules, and exceptions]
Existing software and preferred frontend: [List existing software and preferred coding tools]

Use Swirls as the backend for workflows, agents, durable data, and integrations. Keep the frontend aligned with my chosen tools. Use the Swirls SDK for supported typed interfaces. Enforce business rules and authorization in the backend; do not rely on UI-only checks.

First read the maintained Swirls language skill at https://swirls.ai/.well-known/agent-skills/swirls-lang/SKILL.md and its referenced rules. Follow its complete-system design workflow before writing DSL. If you cannot access those instructions, stop and explain what is missing. Do not invent Swirls syntax, SDK methods, or platform capabilities.

Clarify these questions:
- Who can request and approve a change?
- What changes need a second approval?
- Where do approved changes need to be recorded?

Describe the complete system: interface, roles, access boundaries, data, workflows, agents, integrations, failure handling, and production responsibilities. Identify assumptions and missing capabilities. Present the plan for review before implementation. Treat the client details above as requirements to clarify, not permission to access external systems.

After approval, build in small verifiable steps. Validate .swirls files using the documented tooling. Keep credentials out of prompts and browser code. Assess hosting and networking against the actual runtime; do not assume private connectivity is already configured. Obtain explicit authorization before deploying or changing production resources.

Acceptance checks:
- An unauthorized person cannot approve a change.
- A repeated submission does not create duplicate work.
- The approved change and its history remain traceable.

Report what works, what was tested, and what still requires configuration or review.

Things to test

Check the
app works.

An unauthorized person cannot approve a change.
A repeated submission does not create duplicate work.
The approved change and its history remain traceable.

Change-order control

Describe theapp you want.

Check theapp works.

Describe the
app you want.

Check the
app works.