maccydee

brainstorming

Collaborative, one-question-at-a-time design brainstorming that walks through a system or feature design section by section, always leading with a recommendation, and produces a DESIGN.md at the end. Use when the solution is unclear and needs design refinement first, when asked to "brainstorm", "help me design", "work through a design", "think through the architecture", or before writing an implementation plan. Precedes writing-plans.

executing-plans

Use when handed a complete implementation plan (PLAN.md) to build. Loads the plan, reviews it critically, implements it in small reviewed batches with a test-first cycle, and reports between batches so an architect can catch drift early. Trigger on "execute the plan", "implement this plan", "run the plan", or "start building from this plan". Follows writing-plans.

skeptic

Adversarial reviewer that challenges whether something should be built at all, before challenging how. Use when asked to be a skeptic, "be skeptical", "pressure-test this", "poke holes in this", "play devil's advocate", or "should we even build this?". Applies a blunt YAGNI / over-engineering / scope critique to any artifact, a plan, a design, requirements, a feature request, or code. Complements correctness and security review, which ask whether something is built right; the skeptic asks whether it should exist.

writing-plans

Write an implementation plan (PLAN-*.md) that a zero-context executor can follow to completion: exact file paths, complete code, test-first cycles, and verification steps. Use when asked to "write a plan", "make a plan", "draft a plan", or to turn a design into an implementation plan. Follows brainstorming; precedes executing-plans.

Data & Documents Listed

rate-cv

Rate and critique a CV/resume. Scores it out of 100 against a weighted leadership rubric that adapts to the CV's field (engineering, clinical, teaching, finance, operations), checks ATS parse-ability, quantified impact, and AI-slop, and can match it to a specific job description with a keyword gap list. Use this whenever the user wants a CV or resume rated, scored, graded, reviewed, critiqued, checked against ATS, or matched to a job posting, and also when they ask to improve, tighten, or sanity-check a CV even if they don't literally say "rate". Works on .docx and .txt; pass a job description too for a targeted match.

natural-writing

Write and edit prose that reads as authentically human — voice-driven, specific, and free of the tells that make text sound machine-generated (and that trip AI-detectors). Use this whenever producing or revising reader-facing written content: blog posts, articles, essays, newsletters, marketing and website copy, social posts, product descriptions, cover letters, emails, LinkedIn posts, scripts, or long-form documentation. Trigger it whenever the user asks to "make this sound human," "not sound like AI/ ChatGPT," "pass AI detection," "humanize," "de-slop," "add voice," or to write/rewrite/edit/polish any substantial piece of prose — even if they don't name this skill. Do not use it for code, config, data transforms, or terse factual lookups where prose style is irrelevant.

1 Updated 2 weeks ago