Round 1: Help me build the archive framework
When to use: You're not sure which relationship to start with, or how to design an archive structure that fits you.
I'm working on the '{{route name}}' project using *{{book title}}* and want to build a long-term NVC Communication Growth Archive. My situation: [Fill in: the 1–2 relationships you most want to improve, and the recurring communication patterns you struggle with in those relationships] Please help me: 1. Determine which relationship I should start the archive with, and explain why 2. Suggest what 'baseline information' I should record before the archive begins 3. Give me a first-month archive launch plan (what to log, how often, and how to review at month-end) 4. Remind me what fundamentally distinguishes this archive from a '21-day action plan' — so I don't turn it into yet another plan
Yellow placeholders need you to fill in before using the AI.
AI can help you organize ideas, but cannot make final judgments for you. Don't let AI fabricate experiences, cases, or misleading content.