agentic

Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.

Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.

Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.

Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.

Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.

Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.

Use when building frontend features from idea to implementation. Triggers on new UI components, pages, or features needing design and code.

Use when creating a comprehensive product vision document from a rough idea. Triggers - new product initiative, strategic planning, need rich vision before specs, product direction definition.

Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.

Use when code has mixed concerns, infrastructure dependencies in business logic, or untestable domain rules. Triggers on service design or refactoring requiring decoupled business logic.

Use when implementing code according to a technical plan. After planning, during development.

Use when writing tests, reviewing test quality, debugging flaky tests, or deciding what/how to test.

Use when building web components, pages, or applications requiring high design quality. Triggers on UI implementation, component creation, or polished interface needs.

Use when extracting technical context from codebase and vision docs before planning implementation.

Use when resolving language-specific skills for a workflow. Triggers on multi-language projects or when language-specific conventions are needed before implementation.

Use when producing implementable technical plans with task breakdown and verification matrix. After context gathering, before implementation.

Use when writing TypeScript code - covers types, error handling, style, and patterns

Use when implementing forms, inputs, modals, loading states, or user feedback patterns.

Use when debugging bug reports, CI failures, test failures, runtime errors, or flaky tests. Takes error logs, stack traces, or issue descriptions and systematically investigates to a verified fix. Evidence-based, no guessing.

Use when implementing from a technical plan (from agentic:technical-planning or planning mode). Triggers - "implement this plan", "implement technical plan", technical plan file provided.

Use when reviewing a pull request for code quality, test coverage, and security. Triggers - "review PR", "review pull request", PR number or link provided, code review request.

Use when transforming product specs, epics, stories, or PRDs into detailed technical plans. Triggers - need technical plan from spec, want architecture decisions before implementation, need to resolve all technical open questions before coding.

Use when implementing from a technical plan (from agentic:technical-planning or planning mode). Triggers - "implement this plan", "implement technical plan", technical plan file provided.

Use when resolving language-specific skills for a workflow. Triggers on multi-language projects or when language-specific conventions are needed before implementation.

Use when writing TypeScript code - covers types, error handling, style, and patterns

Use when reviewing a pull request for code quality, test coverage, and security. Triggers - "review PR", "review pull request", PR number or link provided, code review request.

Use when writing Python code - covers typing, error handling, style, imports, and patterns

Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.

Use when producing implementable technical plans with task breakdown and verification matrix. After context gathering, before implementation.

Use when debugging bug reports, CI failures, test failures, runtime errors, or flaky tests. Takes error logs, stack traces, or issue descriptions and systematically investigates to a verified fix. Evidence-based, no guessing.

Use when transforming product specs, epics, stories, or PRDs into detailed technical plans. Triggers - need technical plan from spec, want architecture decisions before implementation, need to resolve all technical open questions before coding.

Use when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.

Use when creating a comprehensive product vision document from a rough idea. Triggers - new product initiative, strategic planning, need rich vision before specs, product direction definition.

Use when code has mixed concerns, infrastructure dependencies in business logic, or untestable domain rules. Triggers on service design or refactoring requiring decoupled business logic.

Use when implementing code according to a technical plan. After planning, during development.

Use when writing tests, reviewing test quality, debugging flaky tests, or deciding what/how to test.

Use when building web components, pages, or applications requiring high design quality. Triggers on UI implementation, component creation, or polished interface needs.

Use when extracting technical context from codebase and vision docs before planning implementation.

Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.

Use when adding security, privacy, or compliance constraints to technical artifacts. Before or after technical planning.