← all publishers

alexandrbasis

@alexandrbasis source repo

Report this profile Claim this profile

• 80 skills
• 0 followers
• 4 hours ago last updated

1. ▌
   Ct 2 · alexandrbasis bundle

   Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
   0 installs
2. ▌
   Nf 2 · alexandrbasis bundle

   Runs an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning. Use when asked to 'detail a feature', 'explore a new feature', 'feature discovery', 'interview about feature', 'spec out a feature', 'design a feature', 'think through a feature', 'deep dive on a feature', 'discover [feature-name]', or 'what should we consider for [feature]'. NOT for quick brainstorming (/brainstorm), PRD/JTBD docs (/product), or implementation tasks (/ct).
   0 installs
3. ▌
   Ph 2 · alexandrbasis

   Prepare session handoff for continuation in a new conversation. Use when 'prepare handoff', 'save progress', 'session handoff', 'I need to stop', 'prepare for next session', 'hand off', 'write handoff', or when the user wants to pause mid-implementation and resume later in a fresh context window.
   0 installs
4. ▌
   QA 2 · alexandrbasis

   Interactive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a dependency-linked breakdown. Explores the codebase in the background for context and domain language. Use when user wants to "do QA", "report bugs", "file issues from a QA pass", or runs through multiple problems at once. NOT for single-bug triage (use /triage-issue) or interactive debug (/dbg).
   0 installs
5. ▌
   Si 2 · alexandrbasis bundle

   Implement or resume a task from its existing plan and acceptance criteria, with behavior-first tests and recorded verification. Use for requested implementation; unresolved discovery belongs to /nf, planning to /ct, and independent review to /sr.
   0 installs
6. ▌
   Sr 2 · alexandrbasis bundle

   Use when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree. Trigger on requests like 'review PR', 'review my changes', 'review this branch', 'is this ready to merge', or other pre-merge review requests. Supports task/spec-aware review when task docs exist. NOT for addressing review comments (use /prc).
   0 installs
7. ▌
   Vp 2 · alexandrbasis bundle

   Create interactive visual prototype playground for user approval before technical decomposition. Use when asked to 'create prototype', 'visual mockup', 'preview design', 'design playground', 'show me the feature', 'what would this look like', 'mockup the UI', 'visualize the architecture', 'preview before building', 'let me see the design', or anytime the user wants to see or approve a visual representation of a feature before coding begins. Also trigger when /nf discovery is complete and the user says 'looks good, let's see it', 'now show me', or 'visualize this'. NOT for brainstorming (use /brainstorm), NOT for feature discovery (use /nf), NOT for implementation tasks (use /ct), NOT for quick one-off diagrams (use /generate-web-diagram).
   0 installs
8. ▌
   Dbg 2 · alexandrbasis

   Debug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate runtime issue', 'it's not working', 'getting an error', 'this crashes', 'unexpected behavior', or when the user pastes an error message or stack trace and wants to find the root cause. Also trigger when the user describes behavior that differs from expectations in a running app. NOT for static code analysis without reproduction (use /code-analysis). NOT for CI pipeline failures (use /fci).
   0 installs
9. ▌
   Fci 2 · alexandrbasis

   Fix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'. NOT for debugging runtime bugs (use /dbg), NOT for code review (use /sr).
   0 installs
10. ▌
    Prc 2 · alexandrbasis

    Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si).
    0 installs
11. ▌
    Rip 2 · alexandrbasis

    Review a technical implementation plan for business-value alignment and scope fit. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review technical decomposition', or 'is my plan aligned with requirements'. NOT for code review (use /sr), NOT for creating tasks (use /ct), NOT for static code analysis (use /code-analysis).
    0 installs
12. ▌
    Sbs 2 · alexandrbasis

    Interactive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me how', 'learn while doing', 'I want to understand', 'help me learn', 'can you explain how', 'what does this do and why', or when the user expresses desire to understand a topic deeply rather than just get a quick answer. Also trigger when the user wants to learn a new tool, library, pattern, or workflow hands-on — even if they don't use the word "teach". NOT for open-ended brainstorming (use /brainstorm), NOT for quick one-off explanations (just answer directly), NOT for debugging (use /dbg).
    0 installs
13. ▌
    Tdd 2 · alexandrbasis bundle

    Test-driven development with red-green-refactor loop using vertical slices. Use when building features or fixing bugs with TDD, when /si or /si-quick needs canonical TDD discipline, when user mentions "red-green-refactor", "tracer bullets", "test-first", or asks for integration-style tests. Forbids horizontal slicing (all tests then all implementation).
    0 installs
14. ▌
    Setup 2 · alexandrbasis bundle

    Configure claudops for a specific repository after copying the workflow or installing the plugin. Use for first setup, requested reconfiguration, or unresolved project placeholders in claudops files.
    0 installs
15. ▌
    Analyze 2 · alexandrbasis

    Compare a task's discovery or product requirements with its tech decomposition and report traceability gaps. Use when asked to 'analyze consistency', 'check alignment', 'verify spec matches plan', 'traceability check', 'spec drift', 'are my docs aligned', or after /ct completes to verify the plan covers the requirements. `/ct` may invoke this check when traceability is material; otherwise it remains an explicit read-only command. NOT for code review (use /sr), NOT for code analysis (use /code-analysis), NOT for debugging (use /dbg).
    0 installs
16. ▌
    Product 2 · alexandrbasis

    Create a JTBD or PRD that records the user problem, evidence, scope, and measurable outcome through an interactive product interview. Use when asked to 'create JTBD', 'write a PRD', 'product requirements', 'jobs to be done', 'product documentation', 'product spec', or when a feature needs formal product-level documentation before technical planning. Conducts research, interviews, and pressure-tests the product thinking before writing. NOT for technical decomposition (use /ct), NOT for feature discovery (use /nf).
    0 installs
17. ▌
    Finisher 2 · alexandrbasis

    Ship an existing implementation by committing local changes, pushing an open PR, waiting for green CI, and merging it. Use when the user explicitly asks to 'merge the PR', 'ship it', 'merge and close', 'commit push merge', 'finalize this PR', or 'land this branch'. Do not trigger on generic end-of-work language without a resolved PR or branch destination. This flow works with or without a task directory; phase handoff details live in Gate 3. NOT for opening a new PR (use plain `gh pr create`). NOT for addressing review comments (use /prc). NOT for preparing a session handoff to a fresh context (use /ph).
    0 installs
18. ▌
    Grill Me 2 · alexandrbasis

    Use when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when the user explicitly says "grill me".
    0 installs
19. ▌
    Quick 2 · alexandrbasis

    Apply a small change with known scope or a diagnosed bug fix using a compact task record. Use for quick fixes, configuration edits and bounded refactors; use /ct when the work needs unresolved design or coordinated implementation planning.
    0 installs
20. ▌
    Zoom Out 2 · alexandrbasis

    Step up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing the bigger picture. Use when user says "zoom out", "give me a map", "I'm lost in this code", or "what calls this".
    0 installs
21. ▌
    Blueprint 2 · alexandrbasis

    Turn a one-line objective into a bounded staged implementation plan with cold-start briefs. Use when asked to 'blueprint', 'multi-session plan', 'long-term plan', 'construction plan', 'break into sessions', 'plan across sessions', 'multi-step project plan', 'session plan', or when work needs staged handoffs. Produces a plan where each step can be resumed independently by a fresh agent with no prior context.
    0 installs
22. ▌
    Cc Linear 2 · alexandrbasis bundle

    Execute Linear operations via direct GraphQL API — create issues, update status/priority/title, add comments, search tasks, manage labels, assign work, and link PRs. Use this skill when the user mentions Linear explicitly, or references a Linear-style identifier (uppercase team prefix + dash + number, e.g. ENG-123, OPS-7; the project's team key is in $LINEAR_TEAM_KEY). Trigger on phrases like "create a Linear ticket/issue", "move TEAM-X to done/in progress/review", "update the Linear task status", "close the Linear issue", "what's in our Linear backlog", "assign this Linear issue to", "my Linear issues", or any project management operation targeting Linear. Also trigger when other skills (ct, si, sr) need to sync state with Linear. Do not trigger on ambiguous "create an issue" when the user clearly means a GitHub Issue (repo context, `gh issue` commands, issues.md), unless they also reference Linear.
    0 installs
23. ▌
    Codex CLI 2 · alexandrbasis bundle

    Run OpenAI Codex CLI for one-shot cross-AI code review or approach validation. Invoke ONLY when the user explicitly asks ('second opinion', 'codex review', 'ask codex', 'run codex', 'cross-AI check'), or when another skill passes an explicit instruction to delegate to codex. Do not invoke proactively on general review requests. Not for interactive conversations.
    0 installs
24. ▌
    Brainstorm 2 · alexandrbasis

    Compare options and clarify a decision through a collaborative brainstorming session. Use when asked to 'brainstorm', 'let's brainstorm', 'explore ideas', 'think through', 'brainstorm about [topic]', 'what are our options for', 'let's think about', 'pros and cons of', 'help me decide', or 'weigh the options'. NOT for feature discovery (use /nf), NOT for PRD/JTBD docs (use /product), NOT for deep research (use /deep-research), NOT for pre-implementation design (auto-triggered by design-exploration skill).
    0 installs
25. ▌
    Cursor CLI 2 · alexandrbasis bundle

    Run Cursor CLI for one-shot cross-AI code review when a Cursor perspective is explicitly wanted. Invoke ONLY when the user asks ('cursor review', 'ask cursor', 'run cursor'), or another skill explicitly delegates to Cursor. Do not invoke it implicitly for a generic review. Not for interactive conversations.
    0 installs
26. ▌
    Dev Server 2 · alexandrbasis

    Start any project's dev server and monitor it for errors in real-time. Universal — works with Node.js (Next.js, Vite, Remix, Astro, SvelteKit, Nuxt, Angular, Gatsby, Expo), Python (Django, Flask, FastAPI, Uvicorn), Ruby (Rails, Sinatra), Go, Rust (Cargo), Java (Spring Boot, Gradle, Maven), PHP (Laravel, Symfony), Elixir (Phoenix), and Docker Compose. Auto-detects the stack and package manager from project files. Uses the Monitor tool to stream only errors, warnings, and crashes — not routine request logs. Use this skill whenever the user says "start dev server", "run dev", "start the app", "launch the server", "npm run dev", "cargo run", "python manage.py runserver", "rails server", "go run", or anything that implies starting a local development server. Also trigger when the user asks to "monitor the server", "watch the build", "check for errors while I work", or simply "dev".
    0 installs
27. ▌
    Udoc 2 · alexandrbasis

    Update documentation for a completed implementation and, when the repository uses one or the user requests it, update its changelog. NOT for creating new product docs (use /product).
    0 installs
28. ▌
    Triage Issue 2 · alexandrbasis

    Investigate a reported bug, find its root cause, and file a tracker issue (GitHub or Linear) with a TDD-based fix plan. Mostly hands-off — minimize questions to the user. Does NOT apply the fix. Use when user reports a bug and wants it tracked, mentions "triage", "file an issue", or "investigate and plan a fix". NOT for interactive debugging (use /dbg) or batch QA sessions (use /qa).
    0 installs
29. ▌
    Update Setup 2 · alexandrbasis bundle

    Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
    0 installs
30. ▌
    Code Analysis 2 · alexandrbasis bundle

    Analyze the structure and quality of the current codebase with evidence-backed metrics, patterns, and recommendations. Use for an explicit code audit, architecture assessment, codebase overview, hotspot/complexity question, module-dependency analysis, or pre-implementation exploration. Do not use for pre-merge review (use /sr), runtime debugging (use /dbg), or external-technology research (use /deep-research).
    0 installs
31. ▌
    Deep Research 2 · alexandrbasis

    Research an external, current, niche, or unfamiliar technical topic with cited evidence. Use for explicit research, comparisons, technology evaluation, migration/dependency decisions, or questions whose answer depends on sources outside the local codebase. Do not use for quick brainstorming (use /brainstorm), feature discovery (use /nf), or static local code analysis (use /code-analysis).
    0 installs
32. ▌
    Git Guardrails 2 · alexandrbasis

    Inspect, install, customize, or troubleshoot the harness-level git safety hook that blocks dangerous git operations (push, branch -D, checkout .) before they execute. Use when the user wants to change which git commands are blocked, verify the guard is wired up, or set it up after a fresh clone.
    0 installs
33. ▌
    Antigravity CLI 2 · alexandrbasis bundle

    Run Google Antigravity CLI (agy) for web-grounded research, cross-AI review, or validation when those capabilities are explicitly needed or another skill delegates to agy. One-shot only; do not select it for an ordinary review without an explicit provider choice.
    0 installs
34. ▌
    Parallelization 2 · alexandrbasis

    Parallelize genuinely independent implementation items when /si or the user asks for parallel work. Use /si directly for one item, dependent work, shared files, or shared mutable state.
    0 installs
35. ▌
    Coding Conventions 2 · alexandrbasis

    Internal reference skill — coding standards and patterns for developer agents. Not user-invocable.
    0 installs
36. ▌
    Design Exploration 2 · alexandrbasis bundle

    Explore codebase and design approaches before implementation. Use when asked 'explore the design', 'how would this fit', 'design exploration', 'what patterns exist for', 'how is X implemented', or when another skill (brainstorm, nf) needs codebase context to ground a design proposal. NOT for code review (use /sr), NOT for static analysis (use /code-analysis).
    0 installs
37. ▌
    Review Conventions 2 · alexandrbasis

    Internal reference skill — shared conventions for all code review agents. Not user-invocable.
    0 installs
38. ▌
    Ubiquitous Language 2 · alexandrbasis

    Build or update a DDD-style ubiquitous language glossary when the user explicitly asks to define domain terms, build/update the project glossary, or harden terminology. For /nf, /product, or /ct context-reading calls, load and report the glossary; for authorized post-grill updates, merge and write it. Do not write for a load-only or explanatory request. NOT for architectural vocabulary (use /architecture-language).
    0 installs
39. ▌
    Architecture Language 2 · alexandrbasis bundle

    Canonical architectural vocabulary — module, interface, seam, adapter, depth, leverage, locality. Use when reviewing architecture, deepening shallow modules, designing interfaces, or evaluating refactor candidates. NOT a domain glossary (use /ubiquitous-language for that).
    0 installs
40. ▌
    Improve Codebase Architecture 2 · alexandrbasis bundle

    Explore a codebase for architectural deepening opportunities: refactors that turn shallow modules into deeper ones with better testability and locality. Use when the user explicitly asks for architecture improvement, refactoring opportunities, or coupled-module analysis. Do not use for pre-merge review (use /sr) or spec gaps (use /ct). Read-only; it does not write code.
    0 installs
41. ▌
    Quick · alexandrbasis

    Apply a small change with known scope or a diagnosed bug fix using a compact task record. Use for quick fixes, configuration edits and bounded refactors; use /ct when the work needs unresolved design or coordinated implementation planning.
    0 installs
42. ▌
    Update Setup · alexandrbasis bundle

    Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
    0 installs
43. ▌
    Cc Linear · alexandrbasis bundle

    Execute Linear operations via direct GraphQL API — create issues, update status/priority/title, add comments, search tasks, manage labels, assign work, and link PRs. Use this skill when the user mentions Linear explicitly, or references a Linear-style identifier (uppercase team prefix + dash + number, e.g. ENG-123, OPS-7; the project's team key is in $LINEAR_TEAM_KEY). Trigger on phrases like "create a Linear ticket/issue", "move TEAM-X to done/in progress/review", "update the Linear task status", "close the Linear issue", "what's in our Linear backlog", "assign this Linear issue to", "my Linear issues", or any project management operation targeting Linear. Also trigger when other skills (ct, si, sr) need to sync state with Linear. Do not trigger on ambiguous "create an issue" when the user clearly means a GitHub Issue (repo context, `gh issue` commands, issues.md), unless they also reference Linear.
    1 install
44. ▌
    Codex CLI · alexandrbasis bundle

    Run OpenAI Codex CLI for one-shot cross-AI code review or approach validation. Invoke ONLY when the user explicitly asks ('second opinion', 'codex review', 'ask codex', 'run codex', 'cross-AI check'), or when another skill passes an explicit instruction to delegate to codex. Do not invoke proactively on general review requests. Not for interactive conversations.
    1 install
45. ▌
    Brainstorm · alexandrbasis

    Compare options and clarify a decision through a collaborative brainstorming session. Use when asked to 'brainstorm', 'let's brainstorm', 'explore ideas', 'think through', 'brainstorm about [topic]', 'what are our options for', 'let's think about', 'pros and cons of', 'help me decide', or 'weigh the options'. NOT for feature discovery (use /nf), NOT for PRD/JTBD docs (use /product), NOT for deep research (use /deep-research), NOT for pre-implementation design (auto-triggered by design-exploration skill).
    1 install
46. ▌
    Cursor CLI · alexandrbasis bundle

    Run Cursor CLI for one-shot cross-AI code review when a Cursor perspective is explicitly wanted. Invoke ONLY when the user asks ('cursor review', 'ask cursor', 'run cursor'), or another skill explicitly delegates to Cursor. Do not invoke it implicitly for a generic review. Not for interactive conversations.
    1 install
47. ▌
    Dev Server · alexandrbasis

    Start any project's dev server and monitor it for errors in real-time. Universal — works with Node.js (Next.js, Vite, Remix, Astro, SvelteKit, Nuxt, Angular, Gatsby, Expo), Python (Django, Flask, FastAPI, Uvicorn), Ruby (Rails, Sinatra), Go, Rust (Cargo), Java (Spring Boot, Gradle, Maven), PHP (Laravel, Symfony), Elixir (Phoenix), and Docker Compose. Auto-detects the stack and package manager from project files. Uses the Monitor tool to stream only errors, warnings, and crashes — not routine request logs. Use this skill whenever the user says "start dev server", "run dev", "start the app", "launch the server", "npm run dev", "cargo run", "python manage.py runserver", "rails server", "go run", or anything that implies starting a local development server. Also trigger when the user asks to "monitor the server", "watch the build", "check for errors while I work", or simply "dev".
    1 install
48. ▌
    Udoc · alexandrbasis

    Update documentation for a completed implementation and, when the repository uses one or the user requests it, update its changelog. NOT for creating new product docs (use /product).
    1 install
49. ▌
    Triage Issue · alexandrbasis

    Investigate a reported bug, find its root cause, and file a tracker issue (GitHub or Linear) with a TDD-based fix plan. Mostly hands-off — minimize questions to the user. Does NOT apply the fix. Use when user reports a bug and wants it tracked, mentions "triage", "file an issue", or "investigate and plan a fix". NOT for interactive debugging (use /dbg) or batch QA sessions (use /qa).
    1 install
50. ▌
    Code Analysis · alexandrbasis bundle

    Analyze the structure and quality of the current codebase with evidence-backed metrics, patterns, and recommendations. Use for an explicit code audit, architecture assessment, codebase overview, hotspot/complexity question, module-dependency analysis, or pre-implementation exploration. Do not use for pre-merge review (use /sr), runtime debugging (use /dbg), or external-technology research (use /deep-research).
    1 install
51. ▌
    Deep Research · alexandrbasis

    Research an external, current, niche, or unfamiliar technical topic with cited evidence. Use for explicit research, comparisons, technology evaluation, migration/dependency decisions, or questions whose answer depends on sources outside the local codebase. Do not use for quick brainstorming (use /brainstorm), feature discovery (use /nf), or static local code analysis (use /code-analysis).
    1 install
52. ▌
    Git Guardrails · alexandrbasis

    Inspect, install, customize, or troubleshoot the harness-level git safety hook that blocks dangerous git operations (push, branch -D, checkout .) before they execute. Use when the user wants to change which git commands are blocked, verify the guard is wired up, or set it up after a fresh clone.
    1 install
53. ▌
    Antigravity CLI · alexandrbasis bundle

    Run Google Antigravity CLI (agy) for web-grounded research, cross-AI review, or validation when those capabilities are explicitly needed or another skill delegates to agy. One-shot only; do not select it for an ordinary review without an explicit provider choice.
    1 install
54. ▌
    Parallelization · alexandrbasis

    Parallelize genuinely independent implementation items when /si or the user asks for parallel work. Use /si directly for one item, dependent work, shared files, or shared mutable state.
    1 install
55. ▌
    Coding Conventions · alexandrbasis

    Internal reference skill — coding standards and patterns for developer agents. Not user-invocable.
    1 install
56. ▌
    Design Exploration · alexandrbasis bundle

    Explore codebase and design approaches before implementation. Use when asked 'explore the design', 'how would this fit', 'design exploration', 'what patterns exist for', 'how is X implemented', or when another skill (brainstorm, nf) needs codebase context to ground a design proposal. NOT for code review (use /sr), NOT for static analysis (use /code-analysis).
    1 install
57. ▌
    Review Conventions · alexandrbasis

    Internal reference skill — shared conventions for all code review agents. Not user-invocable.
    1 install
58. ▌
    Ubiquitous Language · alexandrbasis

    Build or update a DDD-style ubiquitous language glossary when the user explicitly asks to define domain terms, build/update the project glossary, or harden terminology. For /nf, /product, or /ct context-reading calls, load and report the glossary; for authorized post-grill updates, merge and write it. Do not write for a load-only or explanatory request. NOT for architectural vocabulary (use /architecture-language).
    1 install
59. ▌
    Architecture Language · alexandrbasis bundle

    Canonical architectural vocabulary — module, interface, seam, adapter, depth, leverage, locality. Use when reviewing architecture, deepening shallow modules, designing interfaces, or evaluating refactor candidates. NOT a domain glossary (use /ubiquitous-language for that).
    1 install
60. ▌
    Improve Codebase Architecture · alexandrbasis bundle

    Explore a codebase for architectural deepening opportunities: refactors that turn shallow modules into deeper ones with better testability and locality. Use when the user explicitly asks for architecture improvement, refactoring opportunities, or coupled-module analysis. Do not use for pre-merge review (use /sr) or spec gaps (use /ct). Read-only; it does not write code.
    1 install
61. ▌
    Ph · alexandrbasis

    Prepare session handoff for continuation in a new conversation. Use when 'prepare handoff', 'save progress', 'session handoff', 'I need to stop', 'prepare for next session', 'hand off', 'write handoff', or when the user wants to pause mid-implementation and resume later in a fresh context window.
    0 installs
62. ▌
    QA · alexandrbasis

    Interactive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a dependency-linked breakdown. Explores the codebase in the background for context and domain language. Use when user wants to "do QA", "report bugs", "file issues from a QA pass", or runs through multiple problems at once. NOT for single-bug triage (use /triage-issue) or interactive debug (/dbg).
    1 install
63. ▌
    Si · alexandrbasis bundle

    Implement or resume a task from its existing plan and acceptance criteria, with behavior-first tests and recorded verification. Use for requested implementation; unresolved discovery belongs to /nf, planning to /ct, and independent review to /sr.
    1 install
64. ▌
    Sr · alexandrbasis bundle

    Use when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree. Trigger on requests like 'review PR', 'review my changes', 'review this branch', 'is this ready to merge', or other pre-merge review requests. Supports task/spec-aware review when task docs exist. NOT for addressing review comments (use /prc).
    1 install
65. ▌
    Vp · alexandrbasis bundle

    Create interactive visual prototype playground for user approval before technical decomposition. Use when asked to 'create prototype', 'visual mockup', 'preview design', 'design playground', 'show me the feature', 'what would this look like', 'mockup the UI', 'visualize the architecture', 'preview before building', 'let me see the design', or anytime the user wants to see or approve a visual representation of a feature before coding begins. Also trigger when /nf discovery is complete and the user says 'looks good, let's see it', 'now show me', or 'visualize this'. NOT for brainstorming (use /brainstorm), NOT for feature discovery (use /nf), NOT for implementation tasks (use /ct), NOT for quick one-off diagrams (use /generate-web-diagram).
    1 install
66. ▌
    Dbg · alexandrbasis

    Debug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate runtime issue', 'it's not working', 'getting an error', 'this crashes', 'unexpected behavior', or when the user pastes an error message or stack trace and wants to find the root cause. Also trigger when the user describes behavior that differs from expectations in a running app. NOT for static code analysis without reproduction (use /code-analysis). NOT for CI pipeline failures (use /fci).
    1 install
67. ▌
    Fci · alexandrbasis

    Fix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'. NOT for debugging runtime bugs (use /dbg), NOT for code review (use /sr).
    1 install
68. ▌
    Prc · alexandrbasis

    Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si).
    1 install
69. ▌
    Rip · alexandrbasis

    Review a technical implementation plan for business-value alignment and scope fit. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review technical decomposition', or 'is my plan aligned with requirements'. NOT for code review (use /sr), NOT for creating tasks (use /ct), NOT for static code analysis (use /code-analysis).
    1 install
70. ▌
    Sbs · alexandrbasis

    Interactive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me how', 'learn while doing', 'I want to understand', 'help me learn', 'can you explain how', 'what does this do and why', or when the user expresses desire to understand a topic deeply rather than just get a quick answer. Also trigger when the user wants to learn a new tool, library, pattern, or workflow hands-on — even if they don't use the word "teach". NOT for open-ended brainstorming (use /brainstorm), NOT for quick one-off explanations (just answer directly), NOT for debugging (use /dbg).
    1 install
71. ▌
    Tdd · alexandrbasis bundle

    Test-driven development with red-green-refactor loop using vertical slices. Use when building features or fixing bugs with TDD, when /si or /si-quick needs canonical TDD discipline, when user mentions "red-green-refactor", "tracer bullets", "test-first", or asks for integration-style tests. Forbids horizontal slicing (all tests then all implementation).
    1 install
72. ▌
    Setup · alexandrbasis bundle

    Configure claudops for a specific repository after copying the workflow or installing the plugin. Use for first setup, requested reconfiguration, or unresolved project placeholders in claudops files.
    1 install
73. ▌
    Analyze · alexandrbasis

    Compare a task's discovery or product requirements with its tech decomposition and report traceability gaps. Use when asked to 'analyze consistency', 'check alignment', 'verify spec matches plan', 'traceability check', 'spec drift', 'are my docs aligned', or after /ct completes to verify the plan covers the requirements. `/ct` may invoke this check when traceability is material; otherwise it remains an explicit read-only command. NOT for code review (use /sr), NOT for code analysis (use /code-analysis), NOT for debugging (use /dbg).
    1 install
74. ▌
    Product · alexandrbasis

    Create a JTBD or PRD that records the user problem, evidence, scope, and measurable outcome through an interactive product interview. Use when asked to 'create JTBD', 'write a PRD', 'product requirements', 'jobs to be done', 'product documentation', 'product spec', or when a feature needs formal product-level documentation before technical planning. Conducts research, interviews, and pressure-tests the product thinking before writing. NOT for technical decomposition (use /ct), NOT for feature discovery (use /nf).
    1 install
75. ▌
    Finisher · alexandrbasis

    Ship an existing implementation by committing local changes, pushing an open PR, waiting for green CI, and merging it. Use when the user explicitly asks to 'merge the PR', 'ship it', 'merge and close', 'commit push merge', 'finalize this PR', or 'land this branch'. Do not trigger on generic end-of-work language without a resolved PR or branch destination. This flow works with or without a task directory; phase handoff details live in Gate 3. NOT for opening a new PR (use plain `gh pr create`). NOT for addressing review comments (use /prc). NOT for preparing a session handoff to a fresh context (use /ph).
    1 install
76. ▌
    Grill Me · alexandrbasis

    Use when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when the user explicitly says "grill me".
    1 install
77. ▌
    Zoom Out · alexandrbasis

    Step up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing the bigger picture. Use when user says "zoom out", "give me a map", "I'm lost in this code", or "what calls this".
    1 install
78. ▌
    Blueprint · alexandrbasis

    Turn a one-line objective into a bounded staged implementation plan with cold-start briefs. Use when asked to 'blueprint', 'multi-session plan', 'long-term plan', 'construction plan', 'break into sessions', 'plan across sessions', 'multi-step project plan', 'session plan', or when work needs staged handoffs. Produces a plan where each step can be resumed independently by a fresh agent with no prior context.
    1 install
79. ▌
    Ct · alexandrbasis bundle

    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
    1 install
80. ▌
    Nf · alexandrbasis bundle

    Runs an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning. Use when asked to 'detail a feature', 'explore a new feature', 'feature discovery', 'interview about feature', 'spec out a feature', 'design a feature', 'think through a feature', 'deep dive on a feature', 'discover [feature-name]', or 'what should we consider for [feature]'. NOT for quick brainstorming (/brainstorm), PRD/JTBD docs (/product), or implementation tasks (/ct).
    1 install