By lou-k
Coordinates a full brag doc authoring pipeline: artifact ingestion, entry writing, gap analysis, interviewing, and quality review.
Use this agent when a user provides source documents and a project name and needs relevant content extracted into a structured, source-attributed markdown document. <example> user: "I have my performance review, a project brief, and some slide decks for my 'Atlas Recommendation Engine' story." assistant: "I'll use the artifact-ingestor agent to extract only the Atlas Recommendation Engine content from your documents." </example>
Use this agent to create a new brag doc entry or update an existing one. Inputs can include artifact summaries, raw notes, interview transcripts, or partial context. Output is a single Markdown document with YAML front matter that strictly follows spec.yaml. This agent is responsible only for building the brag doc entry. <example> Context: The user has raw notes and source artifacts for a project and wants a new brag doc entry authored from them. user: "I have a design doc and some notes about the Athena recommender project. Can you write a brag doc entry?" assistant: "I'll use the brag-doc-entry-builder agent to draft a new entry from your materials." <commentary> The user has source materials and wants a spec-compliant Markdown entry produced. Use the brag-doc-entry-builder agent. </commentary> </example> <example> Context: A guided interview has just concluded and the answers need to be merged into an existing draft entry. user: "Here are my answers to the interview questions — please update the Athena entry with this." assistant: "I'll use the brag-doc-entry-builder agent to merge your answers into the existing entry while preserving what's already there." <commentary> New structured information needs to be merged into an existing record without overwriting good content. Use the brag-doc-entry-builder agent, which has explicit merge behavior. </commentary> </example> <example> Context: The writer pipeline has finished ingesting artifacts and is ready to produce an initial draft record. user: "Draft a brag doc entry for the search ranking project using the artifact summary." assistant: "I'll invoke the brag-doc-entry-builder agent to produce an initial spec-compliant draft from the artifact summary." <commentary> This is the Record Builder step of the pipeline. Use the brag-doc-entry-builder agent to generate the Markdown file from extracted context. </commentary> </example>
Use this agent to interview the user and fill missing or shallow content in a brag doc entry through conversational, holistic questioning. <example> user: "My entry for the Recommendation Engine project feels thin. Can you interview me to flesh it out?" assistant: "I'll launch the guided-interviewer agent to conduct a targeted interview." </example>
Use this agent for rigorous editorial review of a brag doc entry before it's used for CVs, resumes, or marketing content. Returns a punch list — never rewrites the entry. <example> user: "The story for the Payments Reliability project is ready. Can you do a quality pass?" assistant: "I'll launch the quality-gate-reviewer agent to audit the entry and return a punch list." </example>
Use this agent to audit a brag doc entry against spec.yaml and identify missing or incomplete fields. <example> user: "I've written a new story for the Athena recommender project. Can you check it against the spec?" assistant: "I'll use the spec-gap-analyzer agent to audit the entry and report any gaps." </example>
Writes or updates the "Artifacts / Evidence" section of a brag doc entry. Invoke when you have references to design docs, dashboards, PRs, slides, or other supporting evidence for a project.
Writes or updates the "Contributions" section (Owned / Led / Contributed) of a brag doc entry. Invoke when you have evidence of what the individual did on a project.
Writes or updates the "Endorsements" section of a brag doc entry. Invoke when you have quotes from stakeholders, peers, and/or managers that speak to the individual's impact on a project.
Writes or updates the "Failures / Lessons Learned" section of a brag doc entry. Invoke when you have evidence of things that went wrong, root causes, and what changed as a result.
Writes or updates the "Influence Beyond Code" section of a brag doc entry. Invoke when you have evidence of mentoring, hiring, standards-setting, or cross-team leadership on a project.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI agents I've cooked up.
/plugin marketplace add lou-k/claude-plugins
An agent that helps engineers write brag docs — concise, evidence-rich records of what you built, why it mattered, and what you personally contributed.
Install:
/plugin install brag-doc@lou-k
Use:
/brag-doc:write I just shipped a product -- let's document my accomplishments.
See readme for more info.
npx claudepluginhub lou-k/claude-plugins --plugin brag-docDocumentation review, cleanup, and generation with AI slop detection, style learning, and human-quality writing enforcement
📚 Technical Writer — Technical Documentation Specialist + Knowledge Curator
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses