Add outline-design loop after page completion in Phase 4
After designing a page, the agent asks what's next: outline and design the next page in the scenario [N], return to dashboard [R], or validate [V]. Choosing [N] runs Phase 3's page outline dialog (purpose + exit action) then designs the page, creating a continuous loop. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
739c3c5f80
commit
9b349ab8af
|
|
@ -79,6 +79,29 @@ In Dream mode:
|
|||
|
||||
## AFTER COMPLETION
|
||||
|
||||
1. Update design log
|
||||
2. Suggest next action
|
||||
3. Return to activity menu
|
||||
After finishing a page specification (or all pages in Dream mode), present the user with a choice:
|
||||
|
||||
```
|
||||
Page [NN.step] complete! What would you like to do?
|
||||
|
||||
[N] Next page — outline and design the next step in this scenario
|
||||
[R] Return to Scenario Dashboard — pick a different scenario or activity
|
||||
[V] Validate — audit this page specification
|
||||
```
|
||||
|
||||
### Menu Handling Logic:
|
||||
|
||||
- IF N: Check the scenario's shortest path (Q8) for the next page. If the next page doesn't have a folder yet, run the Page Outline Dialog from Phase 3 (ask the two questions: page purpose + exit action), create the page folder, then design it. In Dream mode, the agent outlines AND designs autonomously, then presents the result.
|
||||
- IF R: Return to the Phase 4 Scenario Dashboard
|
||||
- IF V: Load and execute `./workflow-validate.md`
|
||||
|
||||
### The Outline → Design Loop
|
||||
|
||||
When the user chooses [N], the flow is:
|
||||
|
||||
1. **Outline the next page** — Ask: "What's the point of this page?" and "What does the user do to move forward?" (same as Phase 3's [O] dialog)
|
||||
2. **Create the page folder** with boilerplate spec and Sketches/ subfolder
|
||||
3. **Design the page** — run steps 08-15 for this page
|
||||
4. **After completion** — present this menu again
|
||||
|
||||
This loop continues until all pages in the scenario are designed or the user chooses to stop.
|
||||
|
|
|
|||
|
|
@ -71,6 +71,29 @@ Execute steps in `./steps-s/`:
|
|||
|
||||
## AFTER COMPLETION
|
||||
|
||||
1. Update design log
|
||||
2. Suggest next action
|
||||
3. Return to activity menu
|
||||
After finishing a page specification, present the user with a choice:
|
||||
|
||||
```
|
||||
Page [NN.step] complete! What would you like to do?
|
||||
|
||||
[N] Next page — outline and design the next step in this scenario
|
||||
[R] Return to Scenario Dashboard — pick a different scenario or activity
|
||||
[V] Validate — audit this page specification
|
||||
```
|
||||
|
||||
### Menu Handling Logic:
|
||||
|
||||
- IF N: Check the scenario's shortest path (Q8) for the next page. If the next page doesn't have a folder yet, run the Page Outline Dialog from Phase 3 (ask the two questions: page purpose + exit action), create the page folder, then design it using steps 08-15. This is the **outline → design loop**.
|
||||
- IF R: Return to the Phase 4 Scenario Dashboard
|
||||
- IF V: Load and execute `./workflow-validate.md`
|
||||
|
||||
### The Outline → Design Loop
|
||||
|
||||
When the user chooses [N], the flow is:
|
||||
|
||||
1. **Outline the next page** — Ask: "What's the point of this page?" and "What does the user do to move forward?" (same as Phase 3's [O] dialog)
|
||||
2. **Create the page folder** with boilerplate spec and Sketches/ subfolder
|
||||
3. **Design the page** — run steps 08-15 for this page
|
||||
4. **After completion** — present this menu again
|
||||
|
||||
This loop continues until all pages in the scenario are designed or the user chooses to stop.
|
||||
|
|
|
|||
Loading…
Reference in New Issue