feat: preview task canvases with workspace data (#3887)
This commit is contained in:
@@ -39,7 +39,7 @@ desktop boundaries. Link to an existing UI contract when the feature reuses one.
|
||||
|
||||
## Mobile Design Contract
|
||||
|
||||
When a task changes composition, navigation, overlays, touch behavior, scrolling, or breakpoint behavior, state these choices in the working plan or task notes. Keep them brief; do not create a separate document unless the task already uses a spec or committed plan. For copy, icon, color, or content-only styling inside an unchanged surface, identify the nearest mobile exemplar and the rendered mobile check instead of forcing the full contract.
|
||||
When a task changes composition, navigation, overlays, touch behavior, scrolling, or breakpoint behavior, state these choices in the working plan or task notes. Keep them brief; do not create a separate document unless the task already uses a spec or plan. For copy, icon, color, or content-only styling inside an unchanged surface, identify the nearest mobile exemplar and the rendered mobile check instead of forcing the full contract.
|
||||
|
||||
- desktop user outcome and mobile entry point
|
||||
- nearest shipped mobile exemplar and which interaction/geometry it contributes
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: plan
|
||||
description: Create a committed implementation plan and work orders from approved requirements and current system designs. Use after specification work and before implementation.
|
||||
description: Create an implementation plan and work orders from approved requirements and current system designs. Leave the design package uncommitted for review before implementation.
|
||||
---
|
||||
|
||||
# Create an Implementation Plan
|
||||
@@ -259,6 +259,11 @@ review after the PR opens.
|
||||
|
||||
### 5. End the design turn
|
||||
|
||||
Leave the full design package, including requirements, system designs, ADRs,
|
||||
plan, and work orders, unstaged and uncommitted so the user can review its diff
|
||||
in the workspace. Do not stage or commit these files unless the user explicitly
|
||||
asks. Check `git status --short` and include the changed paths in the handoff.
|
||||
|
||||
Report the requirement IDs, system designs, plan, work orders, dependency
|
||||
order, exact checks, and open risks. For UI changes, also render a compact
|
||||
ASCII preview inline in the final conversation summary; links alone are not
|
||||
|
||||
Reference in New Issue
Block a user