Carry the evidence into PRDs and roadmap reviews. A preview release documented persistent scope display; the next release added a normal setting, a line limit and definition navigation. A later configuration debate ended with maintainers retaining the user/workspace choice principle. Together, these records show why demand, shipped scope and policy decisions need separate labels. Research question What do these sources tell us to include in a requirement record, and which decisions still need our team’s input? Input material Feedback and earlier findings Release descriptions Team constraints and open decisions CCNeed research workflow Start with the decision ahead Give CCNeed the feedback and release records, then explain which part of the product you are planning. Develop a requirement record Ask for the user problem, supporting feedback and candidate scope. Follow up on missing evidence and decisions that depend on your team’s constraints. Review and share the record Check the references, add acceptance checks and share or download the report for the planning discussion. What was requested, what shipped and what was decided Keep code context visible | Current-scope display introduced in a preview | Documented release Limit space; reach a definition | Configurable line limit and Ctrl/Cmd-click navigation | Documented release Who controls display preferences? | Maintainers retained the user/workspace choice principle | Recorded discussion decision Requirement and scope record An evidence-based starting point for the PRD Problem: Readers lose their enclosing context in long code blocks. Candidate scope: Persistent context, a line limit and navigation to the definition. Separate decision: Whether pinned content also needs to be editable. Acceptance checks: Verify visibility while scrolling, the line limit and the intended user/workspace setting behaviour. The requirements record sets out the proposed scope and acceptance checks so the team can assess feasibility, effort and timing. Application example based on public records. The analysis and deliverable illustrate a method, not a customer project or business result.