agentic-workstation

Syncs knowledge to the ai-workspace knowledge base. Use when the assistant discovers new patterns, learns user preferences, or identifies information worth preserving for future sessions. Integrates with dots-workstation-tech-assistant for automatic trigger points.

Interact with Slack workspaces for reading channels/messages, sending messages, adding reactions, and browsing canvases. Use when the user asks about agentic-workstation Slack channels, messages, or notifications — NOT for Slack app development (use the slack-cli skill for that).

ClickUp CLI for managing tasks, sprints, comments, statuses, and Docs. Use when the user needs to interact with ClickUp — creating/editing tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Prefer this CLI over raw API calls.

WHAT — Generate or update documentation from code: README.md from repo structure, CHANGELOG.md from git history, API reference from OpenAPI/GraphQL schemas, and AGENTS.md starters for new projects.

Getting started guide for new agentic-workstation users. Walks through setup validation, the skill/agent hierarchy, and the three most useful commands per role (developer, PM, tech lead). Use when someone is new to the workstation or asks "where do I start?"

UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

WHAT — Recommend the most cost-effective LLM provider for a given task type. Shows estimated cost per run across available providers and integrates with dots-devcompanion llm-status to show what is actually available.

WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend, infrastructure, data, UI/UX, and AI-native structural readiness.

HOW — Run dbt checks as documented in the target repo (parse, compile, test, selective run). Does not configure Snowflake accounts or change cloud security.

WHAT — Create and maintain Architecture Decision Records (ADRs) per the agentic-workstation process. Covers when to write an ADR, required sections, review, and linking to epics/PRs. English for cross-team artifacts unless the user asks otherwise.

WHAT - Capture explicit agreements, terms, parties involved, dates, validity, and linked work items using the agentic-workstation Agreement Document structure.

agentic-workstation Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; org dots-* routing when needed.

WHAT - Draft and review bugs using the agentic-workstation Bug Template; classifies whether an issue should be escalated to incident based on production/user impact.

WHAT - Capture lightweight project, product, or operational decisions that do not require a full ADR; includes rationale, date, owner, and references.

WHAT — agentic-workstation Dev Companion (general): layered companion for client delivery; modes, gates, delegation to dots-workstation-assistant and dots-workstation-workflow-generic-project; no CLI matrices.

WHAT - Default development workflow, task lifecycle, DoR, DoD, validation, and evidence model when a project has no explicit override. Repository instructions still take precedence.

WHAT - Draft and review epics using the agentic-workstation Best Practices Epic Template; includes objectives, success criteria, related tasks, stakeholders, and effort metadata.

WHAT - Draft and review incident reports and RCA notes using agentic-workstation Incident Management guidance; includes detection, impact, timeline, RCA, resolution, and follow-ups.

WHAT - Evidence-based management unit assessment for governance, delivery, collaboration, culture, and AI-native management readiness. Interactive and source-driven before any score is assigned.

WHAT - Create structured meeting minutes from notes or transcripts using agentic-workstation meeting templates, with redaction, action items, decisions, and traceability.

WHAT — Default gate for any deliverable: confirm where the final artifact will be stored and that a human will review, before writing PRDs, TRDs, ADRs, or PR bodies. Repository paths, wikis, and ticket tools differ by engagement; never assume a single location.

WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on agentic-workstation Best Practices. Use before finalizing backlog scope, story/task estimates, or iteration commitments.

WHAT — When the repo has no GitHub PR template, structure the pull-request body using the agentic-workstation default in references/pr-body-default.md. Pair with dots-workstation-output-handshake and github-cli-workflow. Does not open the PR; HOW stays in the forge skill.

WHAT — Draft and review a Product Requirements Document (PRD) using the agentic-workstation template. Business-level requirements, acceptance criteria, and traceability. Does not replace the product owner. English for tickets, PRs, and client-facing text unless the user asks otherwise.

WHAT - Interactive evidence intake for project assessments. Ask the user where each evidence source lives, build an evidence map, track missing evidence, assumptions, freshness, and confidence before any scoring happens.

WHAT - Interactive project assessment router: define assessment scope and units, collect evidence through dots-workstation-project-assessment-evidence, then delegate to technical or management unit assessment skills. Always evidence-based and human-reviewed.

WHAT - Produce spike and research findings using the agentic-workstation spike template; captures purpose, findings, implementation strategy, risks, tradeoffs, open questions, and references.

WHAT - Draft and review technical tasks using the agentic-workstation Best Practices Task Template; includes summary, technical notes, AC, estimate, owner, and due date.

WHAT — Draft and review a Technical Requirements Document (TRD) using the agentic-workstation template, typically from an agreed PRD. Covers architecture, data contracts, technical decisions, risks, and test strategy. English for technical artifacts and tickets unless the user asks otherwise.

Workstation health triage — validate tooling, directory layout, and run dots-doctor with remediation suggestions.

WHAT - Draft and review user stories using the agentic-workstation task template plus the As a/I want/so that format from Best Practices examples.

WHAT - Router for creating and refining epics, user stories, tasks, bugs, and incidents using agentic-workstation Best Practices work item hierarchy.

WHAT — Interactive interview to capture client delivery context and store it inside the user's ~/.ai-workspace (or similar) as packs + knowledge (no client skills). Use when onboarding a new client project or updating an existing workspace context.

WHAT — Generic client delivery: Jira or ClickUp, full repo context, human gates, English traceability on tickets, draft PR via delegated forge skills. Use workspace packs for client/account overlays.

Connects Figma design components to code components using Code Connect mapping tools. Use when user says "code connect", "connect this component to code", "map this component", "link component to code", "create code connect mapping", or wants to establish mappings between Figma designs and code implementations. For canvas writes (Plugin API), install the opt-in `figma-use` pack documented in `docs/SKILLS.md`.

Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.

Create a new blank Figma file. Use when the user wants to create a new Figma design or FigJam file, or when you need a new file before calling use_figma. Handles plan resolution via whoami if needed. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard)

Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes (Plugin API), see the opt-in `figma-use` pack documented in `docs/SKILLS.md`.

Use the Figma MCP server to fetch design context, screenshots, variables, and assets, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

Triage and address open GitHub PR review and conversation comments using the gh CLI. Use when the user wants to "address PR comments", "resolve review threads", or "respond to reviewers" on the current branch's pull request.