Loading...
Loading...
Found 31 Skills
Structured meeting summaries with action items, decisions, and key discussion points. Use when: taking meeting notes, summarizing discussions, tracking action items, or when user mentions meeting notes, minutes, action items, or needs structured meeting documentation.
Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes. Use when the user says "write an RFC", "create a proposal", "I need to propose a change", "draft an RFC", "document a decision", or needs stakeholder alignment before making a major technical or process decision. Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.
Evaluate options for a specific design decision node and recommend one with explicit trade-offs. Use when the design already exposes a concrete choice such as architecture style, state management approach, auth model, storage pattern, sync strategy, multi-agent coordination model, language or runtime, UI framework, data-layer library, or tooling selection. Trigger when the user needs structured comparison and recommendation for a bounded design decision. Do not use for broad design discovery, full-system decomposition, or final readiness review.
Gather phase context through adaptive questioning before planning, clarifying implementation decisions, or exploring gray areas for a phase. Triggers include "discuss phase", "clarify phase", "gather context", "what are the gray areas", and "phase discussion".
Run a high-quality decision process and produce a Decision Process Pack (decision brief/pre-read, options + criteria matrix, RAPID/DACI roles, decision meeting plan, decision log entry, comms, review plan). Use for decision making, decision memo, decision log, one-way door vs two-way door, RAPID, DACI, RACI, exec alignment.
Run high-signal design reviews (design critique / design crit / design feedback) by producing a Design Review Pack: review brief + requested feedback, agenda + facilitation script, feedback log prioritized by Value→Ease→Delight, decision record, and follow-up plan.
Create, update, review, and reference architecture decision records (ADRs) in the current git repository. Use when the user asks messy design questions, wants a design doc turned into ADR draft(s), needs existing decisions checked before implementation, wants gaps surfaced before writing an ADR, or wants future sessions to reuse decisions consistently. Inspect repository code and docs first, ask only for missing decision-critical information, then produce or update ADR files using the repo’s ADR conventions or the defaults in references/.
Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.
Routes human attention to decisions that matter in agent-generated code. Active during planning, implementing, fixing. Defines when and how to place DECISION markers in code comments. Also applies when reviewing a diff/PR on request.
Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.