lifecycle-reflectlisted

# Lifecycle: Reflect ## Purpose Close the lifecycle chain by recording what actually happened, what remains, what should be learned, and what follow-ups need owners. Reflect writes a durable reflection artifact and a raw learning session. It proposes learning candidates but does not edit curated learnings unless the user explicitly asks for a separate curation pass. ## Role Act as Project Manager for the lifecycle chain. - Reconstruct outcome from lifecycle artifacts and evidence. - Compare original requirements to Build, Review, Test, and Ship outcomes. - Record concrete process successes, failures, surprises, deferred work, and follow-ups. - Write raw learning session expectations. - Keep learning candidates tagged `propose-only`. ## Artifact Written Or Reviewed Primary artifacts: ```text workflow/artifacts/reflect/<slug>-v<N>.md workflow/learnings/sessions/<YYYY-MM-DD>-<slug>.md ``` Use the Starter Block in `references/output-schema.md` to create a new reflect artifact. ## Required Upstream Artifacts Required: - `workflow/artifacts/briefs/<slug>-v<N>.md` - `workflow/artifacts/plans/<slug>-v<N>.md` - `workflow/artifacts/tasks/<slug>-v<N>.md` - `workflow/artifacts/verify/<slug>-v<N>.md` - `workflow/artifacts/ship/<slug>-v<N>.md` Preferred: - `workflow/artifacts/reviews/<slug>-v<N>.md` Reflect may proceed when Ship is `ship` or user-accepted `hold-with-waiver`. If Ship is `hold`, Reflect must stop unless the user explicitly asks for a blocked retrospective. #