「sprint」の検索結果

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

日本語の概要は準備中です。原文の説明を表示しています。

Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.

日本語の概要は準備中です。原文の説明を表示しています。

Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.

日本語の概要は準備中です。原文の説明を表示しています。

Kit de ferramentas de product ownership ágil para Senior Product Owner, incluindo geração de histórias de usuário compatíveis com INVEST, planejamento de sprints, gerenciamento de backlog e rastreamento de velocidade. Use para escrita de histórias, planejamento de sprints, comunicação com stakeholders e cerimônias ágeis.

日本語の概要は準備中です。原文の説明を表示しています。

Use quando o usuário menciona issues do Jira (ex: "PROJ-123"), pergunta sobre tickets, quer criar/visualizar/atualizar issues, verificar status do sprint ou gerenciar seu workflow no Jira. Ativa em palavras-chave como "jira", "issue", "ticket", "sprint", "backlog" ou padrões de chaves de issue.

日本語の概要は準備中です。原文の説明を表示しています。

Turns a schedule extract (milestone list or planning tool export) and the period's status notes into a DRAFT plain-language slip explanation: which milestones and activities slipped and by how many working days, arithmetic shown, why per the notes as verbatim fragments with source and date, what each slip pushes next per the extract, and the decision each slip needs framed as a question with the options the notes propose and the owner the governance documents name, every missing fact marked UNKNOWN. Use when the user asks to "explain the schedule slip", "what slipped this month and why", "write the schedule commentary for the steering pack", "put the delay in plain language for the sponsor" or "what decisions do these slips need". Do not use for the weekly status report, use project-status-tracker instead; for cost variances, use budget-variance-explainer; for one sprint's carry-over, use sprint-review-summary. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Marketing project management and execution excellence for B2B SaaS campaigns. Use this skill when coordinating multi-channel campaigns, allocating team resources, planning agile marketing sprints, running QBRs with clients, managing project timelines, balancing marketing workload, or implementing marketing operations scrum. Also triggers on: campaign coordination, resource allocation, agile marketing, sprint planning, client success, QBR, project timeline, marketing ops scrum, workload balancing.

日本語の概要は準備中です。原文の説明を表示しています。

スプリントレビューを実行する。GitHub Issues から完了機能サマリー・未完了分析・レポート生成・Slack通知を自動化する

Use when working with Azure Boards Deep — deep Azure Boards management covering work items, sprints, backlogs, queries, and team velocity analytics. Use when performing deep audits of Azure DevOps Boards, analyzing sprint health, reviewing backlog grooming, or assessing team capacity and velocity across Azure DevOps projects.

日本語の概要は準備中です。原文の説明を表示しています。

repositoryを調査し、`docs/PLAN/YYMMDD_{slug}.md` にPhase、Gate、完了状態、実行ルール、チェック項目を持つ自己完結した永続計画を作成または再構成する。Use when the user asks for simple-plan、チェックリスト式の計画、複数停止点を持つ中規模作業、段階的なapp分割やlocal migration、production前Gate、または既存planの構成変更。単発Sprintでは収まらないが、詳細なworker委任計画までは不要な作業向け。既存planをそのまま実行・再開するだけの場合は使わない。

Swiss industrial-print web prototype. Newsprint canvas, monolithic black grotesque, viewport-bleeding numerals, hairline grid dividers, hazard-red accent, ASCII syntax decoration. Distilled from Leonxlnx/taste-skill `brutalist-skill` (Swiss Industrial Print mode).

日本語の概要は準備中です。原文の説明を表示しています。

Kanban / task board with columns (To do / In progress / In review / Done), draggable-looking cards, assignee avatars, swimlanes, and a top filter bar. Use when the brief mentions "kanban", "task board", "sprint board", "trello", "看板".

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

日本語の概要は準備中です。原文の説明を表示しています。

Read and manage software issues, tickets, projects, and planning data in Linear. Use to review sprints and cycles, identify ticket rollover and release blockers, and update issue status, assignees, priorities, and milestones through Linear's official MCP server.

日本語の概要は準備中です。原文の説明を表示しています。

Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.

日本語の概要は準備中です。原文の説明を表示しています。

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

日本語の概要は準備中です。原文の説明を表示しています。

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

日本語の概要は準備中です。原文の説明を表示しています。

/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation — e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision.

日本語の概要は準備中です。原文の説明を表示しています。

VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.

日本語の概要は準備中です。原文の説明を表示しています。

Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions.

日本語の概要は準備中です。原文の説明を表示しています。

/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

日本語の概要は準備中です。原文の説明を表示しています。

Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.

日本語の概要は準備中です。原文の説明を表示しています。

Emergency fix bypassing normal sprint process — hotfix branch, approvals tracked, backport verified, full audit trail.

日本語の概要は準備中です。原文の説明を表示しています。