---
name: kwark-write-spec
description: Turn an agreed creative-tool flow into a specification with sources, states, permissions, recovery and acceptance criteria.
---

# Specify the agreed work

## Context

- https://kwark.space/designSystem/method/specs-and-handoff.md
- https://kwark.space/designSystem/agents/handoff.md
- https://kwark.space/designSystem/patterns/sharing-and-roles.md

## Work

Start from the accepted journey and scope. Name the source records and stable IDs. Separate personal preferences, the project draft and any issued or exported snapshot. Record what existing data can lack and how the new implementation will read it.

Describe each entry point and relevant state, including empty, loading, read-only, offline, interruption and a concurrent edit. List the shared components and exact APIs from the current system. State how keyboard and phone users reach the same operation.

Trace each user-visible rule to an acceptance criterion. For changes affecting others, identify the point at which the user sees the scope and commits it. Preserve recoverable prior values and make retry idempotent where the action can be repeated.

## Deliverable

A buildable spec with user outcome, flow, record ownership, component list, state behavior, copy, acceptance criteria and unresolved decisions.
