Business & Operations

Complete brand identity design guidance covering brand discovery workshops, moodboard creation, logo suite development, typography systems, color palettes, imagery and photography direction, brand guidelines documentation, deliverables checklists, and the strategic process of translating brand values into a cohesive visual system. Use when the user asks about brand identity designer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

**When to use.** When the channel mix includes Facebook — typically for community groups, older demographics, or as a Meta-ads optimization anchor — and you need a stage assignment for organic presence.

**When to use.** When the user wants partners, creators, or existing customers to drive sales on commission as a scalable Do-stage acquisition channel.

Create the customer-facing Vision Document (IIBA Business Need/Solution Vision) from a discovery session. Triggers: create vision, vision document, concept brief, solution vision.

Startup presentation knowledge — pitch deck structures, board updates, launch decks, palettes, investor-readiness checklists.

Business document workflows for startup founders — reports, quotations, spreadsheets, presentations with professional formatting.

Create and review SRS (IEEE 830) — the internal 'what' stage after BRD. Triggers: create srs, software requirements, functional spec, feature spec, specification, legacy 'create prd'.

Responsive-audit methodology — 6 Playwright detection assertions, 3 fix-confidence tiers, detect-fix-re-verify loop. Loaded by responsive-audit-subagent only, not auto-triggered.

Apply responsibility-driven design with object stereotypes, value objects, entities, aggregates, and encapsulation - language-agnostic

Create Mermaid diagrams as Markdown fenced blocks (native GitHub/GitLab/VS Code rendering); optional mmdc CLI for standalone SVG/PNG.

Automate JIRA ticket status transitions after pull requests are merged, ensuring proper workflow closure

Draft and edit professional business emails — plain human tone free of AI tells; subject lines, openings, replies, point-by-point answers, status updates, follow-ups. Triggers: draft email, write email, email reply, business email, follow-up email, rewrite email, email less AI, client update email.

Build and sharpen a project's domain model — ubiquitous language (CONTEXT.md), ADRs. Use when pinning terminology or recording architectural decisions; changes the model.

Construction business development knowledge — proposal summarization, quotations with cost categories, industry terminology, Atlassian workflows.

Autodesk Civil 3D workflows — corridors, surfaces, alignments/profiles, pipe networks, grading, survey; COM and .NET APIs. Version detection before API advice.

Create and review BRDs (BABOK/IIBA) — the sponsor-level 'why' between customer Vision and internal SRS. Triggers: create brd, business requirements, stakeholder requirements, business need.

Plan a new milestone or extend an existing one step-by-step with review gates. Starts with a grill-design session to clarify requirements, then walks through goal → contract → todo → task specs, pausing for user approval at each step.

Run chief-agent across as many batches as it takes to finish a milestone, writing one report per task instead of one per batch. When a task hits ambiguity, a throwaway decision-support agent proposes options; chief-agent still makes the final call and the report captures the reasoning. Requires goals and contracts to exist. Use "/chief-loop".

Investigate, clarify, estimate, and organise a ticket, its sub-issues, or a tracker project. Publish ticket improvements and deferred stakeholder questions; never implement. Also handles re-triage after replies.

Refresh Dex project context, rules, and repo memory by re-analyzing the codebase and promoting verified observations into reviewable `.dex/` context.

Create an implementation plan from a ticket or user request after gathering project context.

Use when implementing server-side HTTP request handling for a Claude Code compatible Anthropic API gateway, especially /v1/messages, /v1/messages/count_tokens, /v1/files, /v1/models, headers, body fields, beta handling, and gateway routing.

Reference implementation for backend use cases — error handling, structure, and patterns. MUST be loaded when creating or modifying any *.use-case.ts file.

MUST be loaded before ANY commit, push, or branch operation. Never use raw git commit/push — this project uses Graphite (gt). Load this skill first whenever you need to commit, push, branch, or ask about git workflow.