Setting the file. One moment.
Subchapter 28.19
references/phases/feedback/feedback.mdMarkdown2 KBView on GitHub
Collects user feedback. Reuses the shared feedback infrastructure (trace builder) adapted for Heroku-to-AWS’s flat resource model. (Plan-share links are GATED OFF until the landing page ships — see feedback-collect.md Step 3.)
Execute ALL steps in order. Do not skip or deviate.
feedback.json (share-link generation is gated off in its Step 3).This is an optional sidebar phase (_kind: sidebar), not a step on the linear backbone. It is entered only when the user opts in at a feedback sidebar (its _trigger), and it returns control to the flow rather than advancing a current_phase — so it has no _advances_to. SKILL.md decides where the feedback sidebar is offered (see the Feedback & Sharing Sidebars section there).
Read $MIGRATION_DIR/.phase-status.json. Verify phases.discover == "completed".
If not: STOP. Output: “Feedback requires at least the Discover phase to be completed.”
Load references/phases/feedback/feedback-collect.md and follow it. It detects the
IDE + plugin version, builds the anonymized trace (trace.json), presents the survey
link, and writes feedback.json (share-link generation is gated off in its Step 3).
Load references/phases/feedback/feedback-assemble.md (the phase’s assembler) and
follow it to enforce the output gate, update .phase-status.json, and mark the
migration complete. It owns the final artifact-level contract for this phase.