wrap-session
Session Wrap-Up Workflow
Execute this workflow when ending a working session to maintain project continuity.
Execution Steps
1. Identify Project Root
Locate the project root containing README.md and CHANGELOG.md. If uncertain, ask the user.
2. Update README.md
Update the project description and status to reflect current state. Keep changes minimal — only update what has meaningfully changed.
3. Update CHANGELOG.md
Append changes to the [Unreleased] section using Keep a Changelog format. See references/changelog-format.md for format details.
Change categories:
More from product-on-purpose/pm-skills
deliver-acceptance-criteria
Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
120deliver-prd
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
117define-hypothesis
Defines a testable hypothesis with clear success metrics and validation approach. Use when forming assumptions to test, designing experiments, or aligning team on what success looks like.
112discover-competitive-analysis
Creates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.
111deliver-user-stories
Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.
110define-opportunity-tree
Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.
107