StagePreview
Developer harness: turn a bounded package into verified working change.
Inspect the prepared package and repository context, implement bounded scope, then show evidence and any skipped checks for review.
01
What the Developer does
You receive a prepared package from Architect and a chosen code repository. First inspect the WP identity, acceptance, design links and referenced files. If an input is missing or stale, surface that before coding. Then research what the change touches, plan only the needed scope, implement it, and record evidence a reviewer can inspect.
02
The bounded input
In a source-tool workflow, the prepared design may live under a separate product checkout and must be made accessible explicitly. In current Runtime, the selected repo is the code and test root and must already contain the design and manifest inputs it looks up. Neither path silently clones or syncs a sibling repository.
03
Capabilities
- 01
Inspect and plan
Confirm package identity, current code and relevant constraints. Research and specialist agents are used as needed, not a fixed six-agent launch for every request.
- 02
Implement
Make a bounded change in the selected code checkout; keep the plan and evidence tied to the work actually performed.
- 03
Record checks
Show commands and results, including failed or skipped checks. A verdict is specific to the operation; it does not promise every build, test and lint check ran.
- 04
Hand off
Request Quality Harness review. Applying a Quality outcome and publishing through Git are separate approvals; a pushed PR or MR still awaits review and merge.
04
What it hands off
The output is the code change, the implementation record and checkable evidence for Quality Harness. It is not automatically a merged change or an updated product baseline.
05
Going deeper
Start with Claude Code CLI setup, then use the Developer workflow for the repository and handoff details. Claude Desktop/local Runtime has a separate documented setup path.
Read the Developer guide
Bring one prepared WP and inspect its inputs before starting implementation.