emeditor-terminal

Plans a track, generates track-specific spec documents and updates the tracks file

Scaffolds the project and sets up the Conductor environment

Execute a pre-implementation investigation workflow modeled on feature-dev Phase 1-4 (Discovery, Codebase Exploration, Clarifying Questions, Architecture Design). Use this when requirements are ambiguous, architecture decisions are needed, or external validation (Win32 API, Rust crates, EmEditor SDK) is required before coding in Conductor tracks.

Executes the tasks defined in the specified track's plan

Analyzing GitHub Pull Request review comments and managing follow-up tasks. This skill utilizes GraphQL to efficiently fetch review comments and categorizes them into critical fixes, future improvements, or out-of-scope items. Mandatory when a PR has received feedback to systematically address reviewer suggestions and ensure all necessary changes are tracked in Conductor.

Facilitating the creation of Draft Pull Requests on GitHub using the GitHub CLI (gh). This skill guides the collection of branch diffs, issue context via GraphQL, and the generation of structured PR titles and bodies in Japanese. Mandatory when the current task is ready for review as a draft to ensure all necessary context and issue links are included.

Reverts previous work

Reviews the completed track work against guidelines and the plan

Displays the current progress of the project

Standardizing the creation and management of GitHub Issues. This skill MANDATES the use of a specific title format (type - Japanese Description) and a body template including Background/Purpose, Tasks, and Goal sections. It ensures consistency in tracking work items and facilitates clear communication of intent and success criteria. Use whenever creating or updating Issues to maintain project transparency.

Validates the codebase against AcePilot's "Strict Rigid Layered Architecture" rules. Use after implementation tasks or before reviews to ensure physical isolation and dependency direction.

Automates Conductor track cleanup, including archiving, registry cleanup, and project documentation synchronization. Use this when a track is marked as completed in plan.md.

Investigating official Microsoft Learn documentation for Windows API, Win32 system calls, and platform specifications. This skill provides the ultimate reference for HRESULT codes, GDI functions, and COM interfaces. Mandatory when implementing low-level OS interactions or debugging Windows-specific behavior to ensure alignment with official standards.

Executing Spec-Driven Development (SDD) via the Conductor framework. This skill governs track initialization, spec.md/plan.md creation, and the Universal File Resolution Protocol. It mandates strict adherence to phase transition protocols, user manual verification, and checkpointing. Required for all high-level task management and architectural decision-making.

Handles the creation of GitHub Sub-issues. Use this skill when you need to add existing issues as sub-issues to a parent Epic/Issue. It provides the correct usage of the `sub_issue_write` tool and fallback procedures using GitHub CLI (`gh api`) if the tool fails.

Enforcing strict naming standards during refactoring or new entity creation. This skill dictates snake_case for functions/variables, PascalCase for types, and predicate forms (is_xxx) for booleans. It aligns codebase with Domain-Driven Design (DDD) terminology as defined in the ubiquitous language dictionary, ensuring consistency across all modules.

Gitワークフローの詳細なコマンド実行とトラブルシューティング。ステージングの原則は AGENTS.md を参照せよ。

Operates JetBrains IDEs (IntelliJ, etc.) via MCP. Supports project exploration, code reading, structural refactoring, and execution/verification using full IDE capabilities for efficient development.

コミットメッセージの型 (type) 定義と具体例。基本フォーマットは AGENTS.md を参照せよ。

Provides strict JSON schemas for JetBrains MCP Server tools. Use when resolving validation errors due to missing parameters or verifying unknown argument structures.

Replies to specific GitHub Pull Request review threads using GraphQL API. Use when addressing individual review comments.

Mastering Rust/Win32 development by enforcing strict layered architecture (GUI -> App -> Domain <- Infra) and Win32 API isolation. This skill mandates pure Rust domains, RAII-based resource management to prevent GDI leaks, and explicit safety comments for unsafe blocks. Use during code implementation or review to ensure dependency direction and memory safety.

Reasoning through complex engineering problems using a structured "think" tool. This skill is used to analyze ambiguous requirements, verify hypotheses, or break down multi-step tasks into logical components. It enhances meta-cognition by providing a dedicated space for deliberate analysis and reflective problem-solving when navigating intricate technical challenges.