Business & Operations

/requirements - Define Feature Requirements

Run and verify the daily receipt-to-Drive pipeline locally. Scans Gmail for purchase emails, uploads to Google Drive, and emails the configured accounting address.

Interview-based blog post creation that shares hard-won lessons through storytelling. Use when crafting posts about personal learnings, best practices, or experience-based insights.

Use after running tests to clean up test data. Analyzes tenant structure, identifies test-created tenants (empty shells), and safely removes only records with "Test" pattern. Always shows preview and requires confirmation before deletion.

Guides product requirements definition using SVPG principles. Use when defining product requirements, transforming feature requests into problems, or assessing product opportunities. Focuses on problem-first thinking, four-risks assessment, and separating problems from solutions.

Extracts and persists memories from the current conversation to the database. Scans for decisions, preferences, patterns, issues, and learnings, then dispatches the memory-extractor agent. Use manually via /rem-sleep or triggered automatically before context compaction.

Records project events and working sessions to log.md. Default mode captures end-of-session accomplishments. 'refresh' mode queries data sources for external events. Use at end of session, when user says 'log this', or to pull in external timeline events.

Composes, drafts, and sends emails via Gmail. Enforces natural writing style (no em dashes, no AI tells), proper threading, and correct signature handling. Use whenever drafting, replying to, or sending any email.

Creates a project context map by interviewing the user, exploring connected data sources, and scaffolding project configuration (CLAUDE.md, settings.json, custom agents). Use when starting a new project or needing to map all systems of record for a project.

Think through a project change and carry it through the full Emeth Discipline development workflow.

Add the current Emeth Discipline project, or open, inspect, or stop the running Emeth Discipline dashboard server.

Use when design, implementation, or project conversation needs project purpose, operating conditions, domain meanings, or reasons for prior decisions, or when new context needs preservation for later work.

Implement zero-based budgeting processes. TRIGGERS - Use when user needs help with zero-based-budgeting related tasks.

Design workshop agendas with activities, timing, and facilitation notes. TRIGGERS - Use when user wants to plan a workshop, training session, or facilitated meeting.

Create weather risk management plans for farming operations. TRIGGERS - Use when user needs help with weather-risk-plan related tasks.

Design vineyard management plans with seasonal operations. TRIGGERS - Use when user needs help with vineyard-management related tasks.

Design upsell, cross-sell, and expansion revenue strategies. TRIGGERS - Use when user wants to increase average order value, create upsells, or design expansion revenue.

Plan town hall events with presentations and interaction. TRIGGERS - Use when user needs help with town-hall-planner related tasks.

Plan tax season operations with staffing and deadlines. TRIGGERS - Use when user needs help with tax-season-plan related tasks.

Design tax planning strategies. TRIGGERS - Use when user needs help with tax-planning-strategy related tasks.

Design strategic planning processes. TRIGGERS - Use when user needs help with strategic-planning-process related tasks.

Design SLA management with monitoring. TRIGGERS - Use when user needs help with sla-management related tasks.

Design S&OP processes. TRIGGERS - Use when user needs help with sales-operations-planning related tasks.

Design sales operations processes. TRIGGERS - Use when user needs help with sales-operations-plan related tasks.