Config-driven visible plan-to-PR workflow for Workbench engineering work. Use for agent-flow, full lifecycle, visible agents, Helix-style implementation, cross-repo context, HTML plans, PR breakdowns, small or stacked PRs, reviewer packets, review from packet, Claude/Codex pairing, worktrees, Jira/PR handoffs, continuation handoffs, or approved bypass of detailed PR slicing.
Freeform ideation and structured shortlisting. Generates 8-10 approaches including wild cards, then converges on 2-4 viable options with tradeoffs. Use before /forge or standalone for any creative exploration.
Read Outlook Web calendar via Chrome and extract meeting data for capacity planning. Writes to context/active/calendar.md so other skills use real numbers.
Show remaining capacity today and this week by reading daily and weekly plans. Flags overcommitment. Use when checking if there's room for more work.
Read and critically summarize a Confluence document. Surfaces key decisions, gaps, open questions, and suggests review questions.
Create a release branch and managed _release worktree in a Workbench repo using canonical Python worktree tooling. Use when the user wants to cut a release, create a release branch, start a release process, preview the next release branch name, or keep release work out of main/develop.
Mid-day progress check against the daily plan. Scans for new DMs, checks capacity, and helps reprioritize if needed.
An interactive database design interviewer for relational databases (PostgreSQL, MySQL, SQL Server). Conducts a thorough, multi-phase interview to discover entities, user flows, access patterns, edge cases, and scale considerations โ then produces ERD diagrams (Mermaid), access pattern analysis, and pros/cons of design tradeoffs. Use this skill whenever someone says "design a database", "help me think through a schema", "I need to model data for...", "database for a new feature", "walk me through database design", "interview me on my schema", or any variation where they want a guided, conversational approach to relational database design rather than just a schema dump. Also trigger when someone mentions "new database", "data model", "schema design", "ERD", "entity relationship", or "access patterns" in the context of building something new.