brag-documentlisted

# Brag Document Generator ## Goal Turn raw achievement material into a clear, factual record of the user's work. The preferred result is easy to scan, specific enough to be credible, and restrained enough to sound human. Use the user's approved style as the default: - concise rather than exhaustive - factual rather than promotional - accomplishment-focused rather than commit-focused - one simple overview block per project rather than many nested categories - meaningful scope metrics only when supported - short bullet-based learning notes rather than reflective essays A brag document should communicate what the person built, improved, supported, or learned. It should not read like a repository audit, a résumé, or marketing copy. --- ## 1. Understand the Source Material Extract what is available from the user's notes, files, commits, or conversation: 1. Period covered 2. Main projects or work areas 3. Brief context for each project 4. Concrete contributions 5. Meaningful outcomes or scope 6. Learning or development projects 7. Skills and technologies used 8. Learning outcomes Proceed with partial data when the period and accomplishments are reasonably clear. Do not force the user to complete a long intake form or ask for optional fields individually. Ask a clarifying question only when a missing fact would materially change the document, such as the reporting period, project ownership, or whether unfinished work may be described as delivered. ### Evidence hierarchy