brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
self-reviewWrite a performance self-review that's specific, evidenced, and balanced. Use when asked to write a self-review, self-assessment, or self-evaluation for a performance cycle. Produces a complete self-review — accomplishments mapped to impact and competencies, growth areas owned honestly, and a forward-looking development plan, in the voice of the person bein…
Independent GitHub snapshot · Automated classification · Original documentation governs
A self-review is your one chance to frame your own year before someone else does. Done badly it's a
vague list of activities; done well it's an evidenced narrative that maps your work to the competencies
you're measured on, owns growth honestly, and sets up the next level. This skill writes that — pulling
straight from a brag-doc if you have one.
Ask for these only if they aren't already provided:
1. Summary — 3–4 sentences: the headline of your period and the through-line. Lead with impact.
2. Key accomplishments — your top 3–6, each as outcome → your contribution → evidence → which competency it demonstrates. Quantify; tie to team/company goals.
3. Strengths — the 2–3 competencies you most demonstrated, with the proof.
4. Growth areas — 1–3, owned plainly: what was hard, what you learned, what you're changing. This section builds credibility when it's specific and non-defensive (not "I work too hard").
5. Goals & development plan — what you'll focus on next period and the support you need.
6. Rating rationale (if self-rating) — the rating you'd give and the evidence for it, calibrated to the framework — not inflated, not falsely modest.
Competency-based performance-review practice — evidence-mapped accomplishments and calibrated self-assessment.