devpilot-cv-writerlisted

# CV Writer (Senior Software Engineering) ## Overview Good senior-engineer CVs win on **quantified impact, technical judgment, and scope growth** — not on adjectives or technology lists. This skill enforces those standards and, critically, **interviews the user for missing numbers instead of producing confident-sounding vague bullets**. **Core principle:** No bullet ships without a quantified outcome OR a concrete artifact. If the data isn't there, ask — never paper over with fluff. ## When to Use - User asks to write, rewrite, improve, polish, update, or review a CV / resume / résumé - User pastes a CV draft and asks for feedback or edits - User is preparing for senior / staff / principal software engineering roles - User wants to "make their CV stronger" **Do NOT use for:** cover letters, LinkedIn profile rewrites that aren't CV-shaped, recruiter outreach drafts, generic non-engineering CVs. ## The Iron Law **No bullet without a number or a concrete artifact.** If the user-supplied draft doesn't contain the data needed to quantify a bullet, you MUST stop and ask. You may NOT: - Replace the missing number with a strong verb ("scaled", "drove", "led") - Hedge with vague qualifiers ("significantly", "substantially", "high-traffic") - Invent plausible numbers - Keep the bullet unquantified "for now" Concrete artifact = a named system, a measurable scope (rows, services, users, regions), a public link, or a published outcome. If none exist, the bullet doesn't go in.