Productivity

majiayu000 Bundle

Specification-driven development workflow for creating requirements, design, and tasks. Use when the user wants to plan new features, fix bugs with proper specifications, refactor code systematically, or needs help breaking down complex implementation work. Creates requirement-spec.md (Japanese), design.md (Japanese), and tasks.md (Japanese) in RsDT/<feature_name>/ directory.

majiayu000 Bundle

Always use this skill to manage tasks in .dialogue/tasks/. Each task is a separate YAML file for merge-friendly multi-user workflows. Triggers on "create task", "new task", "next task", "update task", "list tasks", "tasks", "active tasks", "task status", "status", "show status", "what's in progress", "what tasks", "pending tasks", "current tasks".

majiayu000 Bundle

Retrieve project-specific insights from file-based memory. Use when working on features, encountering domain-specific questions, or user says "--project-recall" or "--recall" (you decide which scope, may use both). Skip for routine tasks or universal pattern questions (use coder-memory-recall). MUST be invoked using Task tool to avoid polluting main context.

majiayu000 Bundle

Auto-invoke after task completion to extract interview-ready STAR stories from completed work.

majiayu000 Bundle

Run the relevant test suite for the current task by reading TESTING.md, selecting the affected stack, executing tests, and summarizing failures or verification.

majiayu000 Bundle

Promote .agents knowledge.

majiayu000 Bundle

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

majiayu000 Bundle

Bounce-back or delivery failure notices for emails sent to customer addresses.

majiayu000 Bundle

Development guide for the lemline-core module. Use when working with workflow execution (orchestrators,

majiayu000 Bundle

Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots, incorrect codebase assumptions, unnecessary complexity, and performance pitfalls while changes are still cheap

majiayu000 Bundle

This skill should be used when running Phase 4 of the /ds workflow to review methodology, data quality, and statistical validity. Provides structured review checklists, confidence scoring, and issue identification for data analysis validation.

majiayu000 Bundle

Use when the user wants a minimal source-only archive for upload or checkpoint. Creates a tar.gz with just src/ and tests/ directories.

majiayu000 Bundle

Create, modify, and maintain Taskfiles following Task (https://taskfile.dev) best practices. Use when: (1) Creating new tasks or Taskfiles, (2) Modifying existing task definitions, (3) Adding new task includes, (4) Debugging task execution issues, (5) Questions about Taskfile syntax or patterns, (6) Running or understanding "task" commands, (7) Questions about available tasks or task namespaces. Triggers: "taskfile", "Taskfile.yaml", "task command", "task:", "create task", "add task", "task --list", "task tg:", "task inv:", "task wt:", ".taskfiles/", "how to run", "available tasks", "task syntax", "taskfile.dev" This skill covers the repository's specific conventions in .taskfiles/ and the root Taskfile.yaml.

majiayu000 Bundle

Synchronize canvas state across team sessions via git. Ensures all team members see the same product knowledge.

majiayu000 Bundle

Check knowledge flywheel health.

majiayu000 Bundle

Manages project plans with rmplan. Use when the user asks to "generate plan 123" (or any number), "work on plan 123", mentions "rmplan" explicitly, or when you are working on an rmplan task and need to edit plans or add a new plan.

majiayu000 Bundle

Calculate priority score for bugs, issues, or tasks based on severity, impact, and likelihood. Use for bug prioritization, task ordering, or risk assessment.

majiayu000 Bundle

Use when orchestrating parallel phases in plan execution - creates isolated worktrees for concurrent task execution, installs dependencies, spawns parallel subagents, verifies completion, stacks branches linearly, and cleans up (mandatory for ALL parallel phases including N=1)

majiayu000 Bundle

Auto-invoke after task completion to generate powerful resume bullet points from completed work.

majiayu000 Bundle

복잡한 다단계 작업의 진행 상황 추적 및 관리

majiayu000 Bundle

Android-specific code review checklist and MVVM/Compose pattern validation for Bitwarden Android — use this for any review task, even if the user doesn't explicitly ask for a "checklist". Detects change type automatically and loads the right review strategy (feature additions, bug fixes, UI refinements, refactoring, dependency updates, infrastructure). Triggered by "review PR", "review changes", "review this code", "check this code", "Android review", code review requests on Kotlin/ViewModel/Composable/Repository/Gradle files, or any time someone asks to look at a diff, PR, or code changes in bitwarden/android.

majiayu000 Bundle

Implement a scoped OSS PR.

majiayu000 Bundle

Create a task breakdown with acceptance criteria, file scope, and test plan.

majiayu000 Bundle

GIST planning workflow. Structure goals into ideas, steps, and tasks using Gilad's evidence-guided framework.

majiayu000 Bundle

Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting.

majiayu000 Bundle

Build mobile-compatible Obsidian study vaults from academic materials with checkpoint workflow and QA. Battle-tested on 800KB+ projects. Works across CS, medicine, business.

majiayu000 Bundle

Fast semantic code navigation via LSP. Load FIRST before ANY code task - even 'simple' ones. Trigger scenarios: (1) fixing lint/type/pyright/mypy warnings or errors, (2) fixing reportAny/reportUnknownType/Any type errors, (3) adding type annotations, (4) refactoring or modifying code, (5) finding where a function/class/symbol is defined, (6) finding where a symbol is used/referenced/imported, (7) understanding what a function calls or what calls it, (8) exploring unfamiliar code or understanding architecture, (9) renaming symbols across codebase, (10) finding interface/protocol implementations, (11) ANY task where you'd use ripgrep to find code or read-file to view a function. Use `leta show SYMBOL` instead of read-file, `leta refs SYMBOL` instead of ripgrep for usages, `leta grep PATTERN` instead of ripgrep for definitions, `leta files` instead of list-directory.

majiayu000 Bundle

Use when you have a spec or requirements for a multi-step task, before touching code

majiayu000 Bundle

Run automated post-release workflow (eval baselines, dashboard, docs) for AILANG releases. Executes 46-benchmark suite (medium/hard/stretch) + full standard eval with validation and progress reporting. Use when user says "post-release tasks for vX.X.X" or "update dashboard". Fully autonomous with pre-flight checks.

majiayu000 Bundle

> MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

majiayu000 Bundle

This skill should be used when the user asks to 'explore the codebase', 'map architecture', 'find similar features', or in Phase 2 of /dev workflow.

majiayu000 Bundle

End-to-end RNA-seq workflow from FASTQ files to differential expression results. Covers QC, quantification (Salmon or STAR+featureCounts), and DESeq2 analysis with visualization.

majiayu000 Bundle

Complete current JAT task with full verification. Verifies work (tests/lint), commits changes, writes memory entry, closes task, releases file reservations, and emits final signal. Session ends after completion.

majiayu000 Bundle

This skill should be used when the user asks to 'verify completion', 'check that tests pass', 'confirm feature works', or REQUIRED Phase 7 of /dev workflow (final). Enforces fresh runtime evidence before claiming completion.

majiayu000 Bundle

This skill should be used when the user asks to 'verify completion', 'check that tests pass', 'confirm feature works', or REQUIRED Phase 7 of /dev workflow (final). Enforces fresh runtime evidence before claiming completion.

majiayu000 Bundle

コマンド起動の仕組みを整理し、明示起動/自動起動/Extended Thinkingの設計と検証を支援するスキル。 起動フロー、トリガー設計、検証手順を一貫して整理する。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 手順設計 / 目的: 実行フローの最適化 • Human-Computer Interaction (Dix et al.) / 適用: 起動UX設計 / 目的: 誤起動の抑制 • Automation Patterns / 適用: 自動起動設計 / 目的: 安定運用 Trigger: Use when designing command activation flows, defining auto-invocation triggers, or validating command execution paths. command activation, auto invocation, extended thinking, slashcommand, execution flow