Piyaz · Where people and agents share one understanding<br>Skip to content

Piyaz Workspace<br>Where people and agents share one understanding<br>Your team and its coding agents work from the same plan, side by side. Piyaz keeps handing them ready work until the project is delivered. You stay in charge of what ships, and the loop handles the rest.<br>Start building<br>Plugs into the agents you useClaude CodeCodexCursorAntigravity

Why projects drift<br>Agents can do the work but they skip the discipline

The context is lost<br>Close the conversation and everything it knew about your project goes with it. The next one starts from nothing.

The work collides<br>Put two agents on the same project and they quietly redo, or undo, each other's work.

You already have a tracker<br>Your tracker does its job. It holds the ticket and who owns it, and for a team of people that's usually enough. What it can't hand an agent is why the work was scoped this way, or what the last attempt tried.

An agent working alone skips every step you'd insist on from a person: the brief, the agreed definition of done, the plan, the review, the sign-off. It skips them because there's nowhere to put them, and nothing anywhere that says what the work depends on.

Every task explains itself<br>Nobody has to explain the work twice<br>Each piece of work carries its own brief. It says what needs to happen and what finished looks like, and it keeps the decisions and the history behind it. Whoever picks it up, a person or an agent, starts with the full picture, so time goes into the work instead of catching up.

PYZ-101<br>Snap the camera on resize

A phone collapsing its address bar changes the viewport mid-scroll, and the motion setting can flip while the page is open. Both change what the camera should be framing, and animating toward the correction reads as a glitch. The loop re-arms a one-shot snap and lands the new framing in a single paint.

How we know it is done<br>A resize lands the new framing in one paint<br>Flipping the motion setting reframes without a reload<br>Ordinary scrolling still eases into frame<br>Nothing else in the render loop restarts with it

What was decided<br>Snap instead of animate, a camera correcting itself in view reads as a bug<br>Arm the snap inside the loop restart so a new caller cannot forget to

What it touches<br>The render loop restartThe camera keyframe readerThe motion preference store

One shared picture<br>Everyone sees the same project<br>Describe an idea, or point Piyaz at work you have already started, and it breaks it into clear pieces and works out what depends on what. Handovers happen through the project itself, so nobody has to sit in the middle relaying messages. At any moment you can see what is finished, what is ready to start, and what is waiting on something else. And the whole team works on it at once, people and agents side by side.

PYZ-117·claude-codePYZ-118·codexPYZ-128·cursor

Whoever starts a piece of work claims it first, so a person and an agent never land on the same task.

Only pieces that do not depend on each other run at the same time.

Each one works in its own space, so nobody overwrites anybody's changes.

Projects belong to your team. Assign any task to a person or an agent, hand work between them mid-project, and see everything on your own plate in one list.

“A change that does not reach everyone did not happen”

Shared knowledge<br>One place for what your team knows<br>Notes hold the way your team works, and the reason behind decisions nobody will remember in a month. Mark one as always on and it lands inside the brief for every task it covers. The others stay just a title and a line. An agent opens those when the work needs them.

guidance<br>The rules that always apply<br>Always included

reference<br>The detail behind a decision<br>Read when needed

knowledge<br>What the team has learned<br>Maintained by agents

Agents can add to it freely, and anyone can search what they add straight away. But it only starts shaping other people’s work once a person says so. An agent can ask for that. It cannot decide it.

The loop<br>Work keeps moving until it is done<br>01Plan it

Describe what you want. Piyaz asks the questions a good lead would ask, pushes back on the weak parts, and turns the answer into clear pieces of work.

02Pick it up

Ask what to work on next and Piyaz names the piece that matters most, hands over the full background, and records what happened when it is finished.

03Review it

Nothing we ship promotes its own work to done. A second agent reviews it first and comes back with approve, changes needed, or stop, pointing at exactly what it found.

04Or hand the loop to Composer

In Claude Code, Composer runs the cycle on its own: research, plan, build, review, fix, then the next piece. It keeps going until the work is done, and you stay the one who approves.

PYZ-133<br>❯ Reading the brief and everything decided so far<br>❯ Writing the plan and agreeing what done means<br>❯ Doing the work and recording what it did<br>❯ Handing it to you for the final...