jira-ticket
Proactively use this skill when you need to read, create, update, or manage Jira tickets.
Essential command-line tools and system utilities.
Proactively use this skill when you need to read, create, update, or manage Jira tickets.
This skill should be used when the user asks to "coordinate document writing", "manage doc writers", "create a design document with multiple writers", "orchestrate documentation", "delegate doc sections", "cos for documentation", "chief of staff for docs", or needs to break a large document into sections and delegate writing to multiple agents via VibeKanban.
[Task Mgmt] A Skill that syncs task status in Docs/Task/{StepName}_Task.md by moving tasks between sections (Backlog, Worker1, Worker2, Worker3, Review, Done) with priority-aware management for multi-agent parallel development. AI agent MUST invoke this skill AUTOMATICALLY when (1) starting work on a task - move to assigned Worker, (2) AI completing work - move to Review (NOT Done). CRITICAL - AI CANNOT move to Done or Backlog. Only User/Reviewer can move tasks to Done or Backlog. (user)
Use this `codex-mcp` skill to instruct another AI Agent to invoke a tool or execute a workflow on your behalf for the following scenario, 1.When you are requested to invoke a mcp tool that you don't have access (can use `ListMcpResourcesTool` to check) such as `context7`, `github`, `linear`, `jira`; 2.When you are requested to execute a complex workflow that require interacting with multiple mcp tools and bash CLI commands for example `github-project-create-items`, `github-project-list-items` workflows;
Manage Todoist tasks via the `todoist` CLI. Use when the user asks to add tasks, complete tasks, list today's tasks, search tasks, manage projects/labels/sections, or interact with Todoist in any way.
Scan ~/dev recursively for git repos and report today's work with commits, branches, stats, and detailed change analysis. Use when user asks "what did I work on", "show my work", "daily summary", "what repos did I touch".
Multi-project dashboard for managing PopKit-enabled projects. Shows health scores, recent activity, and quick actions across all registered projects. Use when switching between projects, checking overall status, or managing project registry. Do NOT use if only working in a single project - use morning routine or next-action instead.
Proactive workflow for projects using beads issue tracker. ACTIVATE AUTOMATICALLY when session starts in directory with .beads/. Use when: starting work session, selecting tasks, completing tasks, creating subtasks. Triggers: "какие задачи", "что делать", "готово", "done", "следующая задача", "создай задачу", "tasks", "next task", "pick task", "обнови задачи", "refresh", "sync".
Developer reporting skill for work documentation and communication. Use when writing journals, devlogs, status updates (22A/22B), progress reports, or documenting development work. Generates reports from git history or manual input.
Track feature implementation status against requirements documents. Provides hierarchical FR code tracking, phase management, and sync with work-overview.md and TODO.md.
Manages Basecamp todos, cards, messages, and projects using the bc4 CLI tool. Use when the user mentions Basecamp, asks about todos or tasks on a card table, wants to create or update Basecamp items, or references team project management.
Track and integrate external communications (emails, chat messages, screenshots) into project context with timeline management. Use when user mentions "email", "message", "communication", "screenshot", "track", "import", "sync", or wants to import external information sources into the project timeline.
This skill should be used when the user asks to "research the codebase", "understand how X works", "explore the code", "gather context", "investigate the implementation", "analyze the architecture", or invokes the rpikit:research command. Provides methodology for thorough interrogation and codebase exploration before planning or implementation.
[Task Mgmt] A Skill that adds new tasks with priority tags to Docs/Task/{StepName}_Task.md documents for multi-agent parallel development. AI agent MUST invoke this skill AUTOMATICALLY when (1) discovering new work items during implementation, (2) user requests a new feature/fix, (3) breaking down a large task into subtasks, (4) identifying follow-up work after completing a task. CRITICAL - Never modify document structure, only add tasks with proper priority tags (!high, !medium, !low). Tasks should be distributed to avoid file conflicts between workers. (user)
Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.
Performs in-depth codebase exploration at the start of a coding session. Builds comprehensive understanding of project structure, architecture, key components, and patterns. Use when starting a new session, when asked to understand or explore the codebase, when asked "what does this project do", when exploring unfamiliar code, or when the user asks about project structure or architecture.
Discover available Jira fields for a project and issue type. Use when the user needs to find field names, see what fields are available, or discover custom field values before creating or updating tickets.
Create Excalidraw diagrams as JSON files for flowcharts, user journeys, system architectures, wireframes, and visual documentation. Use when the user asks to create diagrams, flowcharts, visual representations, architecture diagrams, mind maps, or any Excalidraw-compatible visualizations. Outputs .excalidraw.json files that can be opened in excalidraw.com or any Excalidraw-compatible app.
Start-of-day setup and readiness routine. Calculates Ready to Code Score (0-100) based on session restoration, service health, dependency updates, branch sync, PR reviews, and issue triage. Automatically captures session state to STATUS.json. Use at start of work day after opening Claude Code.
Structured completion workflow for implementation work. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. Guides merge, PR creation, or cleanup decisions.