bob-moesta-advisor
Act as Bob Moesta, innovation expert and co-creator of Jobs to Be Done theory. Use when users want advice on innovation, product development, customer research, sales strategy, understanding why customers buy,...
Discover blockchain project management skills, compare source repositories and read the instructions for each workflow.
Act as Bob Moesta, innovation expert and co-creator of Jobs to Be Done theory. Use when users want advice on innovation, product development, customer research, sales strategy, understanding why customers buy,...
When the user asks about roadmap planning, sprint planning, milestone estimation, or capacity planning
When the user asks about ClickUp synchronization or syncing roadmaps with ClickUp
Use when asked to reflect on how the session went
Tracks and monitors GitLab merge request activity including comments, status, and real-time updates
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sp...
This skill should be used when users need to create Jira tickets for the RD (Research & Development) project. It supports creating features, bugs, and tasks with proper field mapping including assignee, team, s...
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not...
Plan and document features before implementation using project templates. Use when planning new features, creating architecture docs, or when user mentions "plan", "design", "architect", "feature plan", "implem...
Your approach to handling standards summary. Use this skill when working on files where standards summary comes into play.
Your approach to handling backend state management. Use this skill when working on files where backend state management comes into play.
Provides domain knowledge and rules for Todo task management systems.
Defines the overall project purpose, operating model, and roles for Hackathon II – Todo Spec-Driven Development. Always load for any project-related task.
Проводит интерактивное недельное планирование по методологии Дорофеева. Собирает данные из Singularity, Google Calendar, новости, погоду. СПРАШИВАЕТ пользователя о просроченных задачах, входящих задачах, распре...
当用户需要分析文件内容、统计文件信息、或对文件进行深度检查时使用此skill。它可以帮助分析文件结构、代码质量、文件大小等。
Generate WaveJSON timing diagrams for digital signals and create HTML viewers to display them. Use when documenting signal timing, creating timing diagrams, analyzing protocol sequences, visualizing digital wav...
Analyze current spec completion status and provide detailed progress report. Use when checking progress, identifying blockers, or planning what to work on next. More detailed than the /spec-flow:status command.
Break down a spec section or milestone into actionable, session-sized tasks. Use when a milestone is too large, when starting implementation, when the user asks to break down work, or when refining task granula...
Create or update project specifications interactively through an interview process. Use when starting a new project, adding major features, or when the user asks to create a spec, plan a project, or define requ...
Manage project tasks. Create, list, update, and track dependencies of tasks.
Categorize extracted information into the appropriate knowledge base subdirectory (tasks, definitions, wiki, project-status, people, jira-drafts). Use when organizing extractions into the knowledge base.
Persistent schema-driven running log with three-component architecture - quick-capture ideas, AI auto-detection, and backlog review librarian
Track and update progress on system design gap implementation. Use when implementing patterns, marking items complete, checking progress, viewing remaining items, or updating the implementation plan. Triggers o...
Audit a repository's structure and propose a safe, approval-gated reorganization plan. Use when asked to review repo anatomy, propose folder changes, or apply an approved reorg with rollback.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.