김경종
36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
# Step 5: feedback-setup
|
|
|
|
## Read First
|
|
- /AGENTS.md
|
|
- /docs/PRD.md
|
|
- /docs/ARCHITECTURE.md
|
|
- /docs/ADR.md
|
|
- /docs/UI_GUIDE.md
|
|
- /docs/RESEARCH_LOG.md
|
|
- /docs/REPORT_DRAFT.md
|
|
- /docs/FEEDBACK.md
|
|
- /phases/0-report-generation/index.json
|
|
|
|
## Task
|
|
Prepare the report for user review.
|
|
|
|
Update `docs/REPORT_DRAFT.md` with focused feedback questions that help the user decide the next iteration. Update `docs/FEEDBACK.md` with a new pending feedback entry that names the draft version, review focus, and next questions.
|
|
|
|
If the report still has material evidence gaps, list them clearly in both `docs/REPORT_DRAFT.md` and `docs/FEEDBACK.md`.
|
|
|
|
## Acceptance Criteria
|
|
```bash
|
|
python scripts/validate_workspace.py
|
|
```
|
|
|
|
## Verification
|
|
1. Run the acceptance command.
|
|
2. Confirm `docs/REPORT_DRAFT.md` is ready for user review.
|
|
3. Confirm `docs/FEEDBACK.md` has a pending entry for the next iteration.
|
|
4. Update this step in `phases/0-report-generation/index.json`.
|
|
|
|
## Do Not
|
|
- Do not mark unresolved evidence gaps as finished.
|
|
- Do not ask generic feedback questions that do not help revise the report.
|
|
- Do not start a second revision phase in this step.
|