Studio Pull Requests
This directory contains executable plans for Studio work.
Purpose
A Studio pull-request or plan artifact packages a decision into an implementable sequence.
Use it to:
- separate shell work from workspace work,
- describe service and event-lane integration steps,
- define acceptance criteria for UI behavior,
- make validation and regression risks explicit before code changes.
Expected Format
A Studio plan should usually include:
- Briefing
- Objective
- Dependencies
- Scope
- Non-Goals
- Execution Method
- Acceptance Criteria
- Validation
- Affected Artifacts
Writing Rules
- Organize by execution sequence, not by brainstorming.
- Keep visual design, interaction behavior, and service integration clearly separated.
- State what the user should be able to do after the change lands.
- Tie the plan back to Studio specs and decisions explicitly.
Current Queue
The current Studio execution queue is: