After ship and feedback, users obtain a polished end-to-end process document suitable for portfolio, case-study, or stakeholder-retrospective use.
As a user, I want a comprehensive document that summarizes my entire product evolution from idea to shipped product, So that I can use it as a portfolio piece, case study, or stakeholder retrospective — showing the evolution, not just the result.
Maps to: FR47.
Acceptance Criteria:
Given the workspace has completed at least step 11 (Ship); post-ship metrics from step 12 are optional inputs
When the user triggers Portfolio Document generation
Then the system produces a single structured document covering: original problem & hypothesis, discovery insights & key decisions (from step 1 Kitchen Sink framework), concept evolution (before/after at each stage — step 2b concepts → step 5.25 refined designs), design decisions & rationale, three-pillar analysis highlights (per-pillar rankings + release allocation reasoning), architecture choices, the build process, QA & security findings, final product screenshots, key post-ship metrics (if available), and lessons learned
And the document shows the evolution, not just the result — emphasizing how the product evolved through the structured process
And lead agents are John (PO) and Kinsley (Product Designer) per pipeline assignment
As a user, I want to adjust tone, audience framing, and which sections appear in my Portfolio Document, So that the same source produces the right artifact for a portfolio reviewer vs internal retrospective vs case study.
Maps to: FR47.
Acceptance Criteria:
Given an initial Portfolio Document has generated
When the user enters customization mode
Then the user can toggle section visibility, adjust tone (portfolio-friendly / retrospective / case-study), and edit content inline
And the source data remains untouched — customization is a view over the source
As a user, I want to export my Portfolio Document as HTML, PDF, and Doc, So that I can share it on any platform my audience uses.
Maps to: FR47.
Acceptance Criteria:
Given a finalized Portfolio Document
When the user exports
Then the system produces HTML (web-viewable, linkable), PDF (presentation-ready, shareable), and Doc (editable)
And all three formats render from the same source so content does not drift
As a user, I want to generate a Case Study that is shorter and more polished than the Portfolio Document, So that I have a shareable artifact for portfolio reviewers, prospective clients, or a public audience without sending them a long retrospective.
Maps to: FR60.
Acceptance Criteria:
Given the workspace has completed step 11 (Ship) at minimum
When the user triggers Case Study generation
Then the system produces a single-narrative document covering: one-line positioning, the problem, the approach, key decisions (with brief rationale), the team (agents involved), build stats (days, stories, ship date), what worked, what was hard, takeaways
And output is distinct from the Portfolio Document: shorter, polished, and externally shareable
And both documents pull from the same source of truth (audit trail, filter decisions, rationale log) so they stay consistent
And the Case Study can be generated before the Portfolio Document is finalized (they are independent)
As a user, I want the system to proactively offer to generate my Portfolio Document and Case Study at the end of the pipeline, So that I do not leave value on the table by forgetting to produce these artifacts after shipping.
Maps to: FR61.
Acceptance Criteria:
Given the user has completed pipeline step 12 (post-ship feedback)
When the system detects step 12 completion
Then the system surfaces a prompt asking: "Generate Portfolio Document, Case Study, or both?"
And the prompt offers tone options: Portfolio reviewer (short, polished), Internal retrospective (longer, candid), Public case study (mid-length, shareable)
And the user can dismiss the prompt and return to it later from the pipeline view
And declining does not block access to the final step (Portfolio); user can always generate manually
As a user, I want my generated Portfolio and Case Study to look like the product I built, So that every artifact carries my product's visual identity instead of a generic default.
Maps to: FR62.
Acceptance Criteria:
Given the workspace has an established visual identity (design tokens from step 5.25 and/or a brand palette)
When the user generates the Portfolio Document or Case Study
Then the output applies the user's project color palette, typography, and logo
And HTML, PDF, and Doc versions all reflect the same brand identity
And a fallback neutral theme is used if no brand identity is defined (e.g., early ship before design refinement)
And Quorum's own meta case study (case-study.md in this planning repo) serves as a worked example of the pattern
As a user, I want to publish my Case Study to my own portfolio endpoint, So that I can share a canonical live URL that updates as my product evolves, instead of mailing a PDF each time.
Maps to: FR63.
Acceptance Criteria:
Given a finalized Case Study
When the user selects "Publish to portfolio"
Then the user can choose an endpoint: Quorum-hosted share link (default), Connected portfolio website (V1 integration list TBD, e.g., personal site, GitHub Pages, Notion), or Copy published URL for manual publishing
And the published URL is canonical: updates to the source Case Study propagate to the live page on republish
And published case studies carry a visible "last updated" timestamp
And user can unpublish at any time
And publishing requires no additional user credentials beyond Quorum auth for the default Quorum-hosted option