step-analysis
Analyzes why Buildkite pipeline steps were skipped, didn't run, or behaved unexpectedly. Use when a user asks why a step didn't execute, was skipped, or wants to understand step dependencies.
Boost efficiency with task automation and organizers.
Analyzes why Buildkite pipeline steps were skipped, didn't run, or behaved unexpectedly. Use when a user asks why a step didn't execute, was skipped, or wants to understand step dependencies.
Manage GitHub Project board items - add issues, update status, move between columns. Use when user asks to add issues to board, change status, or organize the project.
This skill should be used when the user asks to "create issue", "search issues", "update ticket", "check notifications", mentions "Backlog", "バックログ", "課題", "チケット", discusses project management with Nulab Backlog, or needs to interact with Backlog API for issue tracking.
Knowledge about the context branch methodology for separating AI configuration from project code using git worktrees. Use when users ask about worktree structure, branch organization, or the separation of concerns pattern.
Complete CRUD for SDLC documentation (stories, tasks, context retrieval). Use when creating/managing stories, creating/managing tasks, updating task state, or retrieving full context for any user story via index (<3min restoration).
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Analyze GitHub Actions CI failures for the current branch. Use when the user asks about CI status, test failures, build errors, GitHub Actions problems, or mentions checking CI, workflow failures, or pipeline status.
Creates User Stories from UI screens using component-based decomposition. Analyzes screenshots or screen descriptions to identify UI components and generates User Stories with AMP acceptance criteria (Acceptance, Measure, Proof). Follows T-Minus-15 process template.
Dispatch milestones to user-facing timeline. Use when completing significant steps: starting major phases, calling external APIs, creating external references, completing database operations, or validating Pydantic models. Never dispatch every tool call or internal logs. Environment variables FULCRUM_DISPATCH_URL, FULCRUM_DISPATCH_TOKEN, FULCRUM_TICKET_UUID, and FULCRUM_RUN_UUID must be set (injected by system).
GitHub Issue resolver skill that analyzes, triages, and proposes solutions for issues with full SDD integration Trigger terms: resolve issue, fix issue, github issue, issue triage, issue analysis, issue to PR, issue resolution, auto-fix issue Use when: User requests involve GitHub issue analysis or resolution
Use this skill to start work on an assigned GitHub issue. This is the core implementation loop of the SynthesisFlow methodology. Guides the AI to load full context (specs, plans, retrospective), create a feature branch, and begin implementation. Triggers include "start work on issue", "implement issue
Export user story acceptance criteria from Azure DevOps by ID and optionally generate requirement analysis and test cases. Use this skill when the user wants to export a user story from Azure DevOps, create test documentation, or generate a complete test package from a user story ID.
Git branch, commit, and PR management. Use for version control operations and maintaining clean git history.
Hybrid orchestrator + scrum master + tech lead that scopes requests into work items, routes to the right agents, enforces gates (review/QA/security/devops), prevents loops/thrash, maintains single-source-of-truth status/ledger, and outputs an Orchestrator Update. Use when coordinating multi-agent delivery, managing handoffs, or deciding Done/Rest for work items.
Git コミットワークフローの実行。変更のステージング、コミットメッセージ生成、コミット実行を行う。Use when user wants to commit changes, create a commit, or stage and commit files.
Call Azure DevOps REST APIs via az devops invoke command. Use when you need to access Azure DevOps features not available in the CLI, such as work item comments, search, boards, backlogs, capacities, or any wit/work/search API endpoint. Use when the user mentions "invoke", "REST API", "API call", or needs features like comments, search, board columns, or team capacity.
Generates comprehensive context summaries for async team handoffs. Use when user says "create handoff", "handoff summary", "I'm leaving for the day", or needs to pass work to another team member.
Interact with GitHub using the 'gh' command-line tool for repository operations, issue management, pull requests, GitHub Actions workflows, releases, and gists. Use when working with GitHub repositories, when the user mentions 'gh' commands, GitHub operations, or requests like creating issues, managing PRs, viewing workflows, creating releases, or working with gists.
Set up Composio MCP, connect external apps, manage integrations, use RUBE tools. Use when connecting apps, setting up integrations, using Composio, Gmail, Calendar, or any external service automation.
Expert guidance for creating weekly status reports for 8090 project management teams. Use when generating status reports, weekly updates, project progress reports, or team updates. Automatically finds previous week's report, gathers context from project files and meeting notes, and generates comprehensive status updates following the standardized format. Triggered by requests like 'create status report', 'generate weekly update', 'prepare project status', or 'create this week's status report'.
Distill rough ideas into structured project specs with issues. This skill takes unstructured input (bullet points, rough notes, transcribed ideas) and systematically breaks it down into feature domains, uses sub-agents to deeply analyze each domain, identifies ambiguities requiring user clarification, and ultimately produces a structured spec with actionable issues. Use this skill when the user wants to transform rough project ideas into well-defined specifications and issues, or when they invoke /speccer.