decision-record
Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.
Write and read the between-session handoff file so a fresh agent with no memory can pick up where the last one stopped without re-deriving context. Structured prose, not JSON — the model writes prose better.
Negotiate a pre-code contract between generator and evaluator personas that defines what "done" means before any code is written. Turns fuzzy specs into a testable target the evaluator can hold the generator to.
Drafts a concise weekly status-update email to the user's team, covering open tasks, upcoming meetings, and action items, with light emoji formatting in the body. Use when the user asks to "draft my weekly status email", "write my weekly team update", "send my team the weekly status", "create my Monday status mail", "weekly status update for the team", or "recap this week for the team". Do NOT use for leadership or executive updates and cross-functional stakeholder communications — use stakeholder-comms instead. Do NOT use for one-off announcements or non-status emails — use the Outlook tools directly.
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Use when asked to "plan implementation", "design approach", "architecture plan", "how should I implement", "what files do I need", or to create a design doc before writing code.
Refine requirements, analyze a ticket, perform gap analysis, or clarify what a Jira/Confluence ticket is asking before coding in Bitwarden iOS. Use when asked to "refine requirements", "analyze ticket", "gap analysis", "clarify ticket", "what does this ticket mean", or to understand scope before implementation begins.