メニュー
Stage 1: Ticket Intake - Understand what to build before coding begins. Identifies architecture layers, anticipates classes, determines test types, flags ambiguities. Trigger: "read ticket CA-123", "analyze ticket", "what does CA-456 require"
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | read-ticket |
| description | Stage 1: Ticket Intake - Understand what to build before coding begins. Identifies architecture layers, anticipates classes, determines test types, flags ambiguities. Trigger: "read ticket CA-123", "analyze ticket", "what does CA-456 require" |
| disable-model-invocation | false |
Verb: Understand what to build.
Agent's first action when assigned a story. Output primes plan-implementation and subsequent coding skills.
ticket_id: YouTrack ID (e.g., "CA-123")output_format (optional): structured or conversationalFetch ticket via mcp__youtrack__get_issue(issueId: ticket_id)
Identify layers touched (presentation, domain, data, integration)
Anticipate classes (rough scope, not final naming)
Determine test types
skills/rules/13-mutation-testing.md)Flag ambiguities
plan-implementationOutput analysis
Conversational (default):
📋 Ticket CA-123: Add project estimation page
Layers: Presentation + Domain
Classes: EstimationPage, EstimationBloc, GetEstimationsUseCase
Tests: Unit + Widget + Golden
⚠️ Ambiguities:
- No API endpoint specified
- No error handling mentioned
**Next:** Clarify ambiguities, then plan the implementation using the plan-implementation skill
skills/plan-implementation/SKILL.mdStage 3: Coding (Data Layer) - Write RepositoryImpl, DataSources, and DTOs. Data layer implements repository interfaces and handles external data sources (API, DB, cache). ⚠️ INVOCATION: Only use when the ticket touches the data layer (repository implementations, data sources, API/DB access). Trigger: "write data code", "implement data layer", "create datasource" (DataSource interface + related data layer classes)
Stage 3: Coding (Domain Layer) - Write UseCases, Repositories (interfaces), and Services. Domain layer contains pure business logic with no knowledge of UI or data sources. ⚠️ INVOCATION: Only use when the ticket touches the domain layer (business logic, use cases, repository interfaces). Trigger: "write domain layer code", "implement domain layer use cases", "create domain usecase"
Stage 3: Coding (Integration Layer) - GATED - Only for new third-party SDK integrations. Creates wrapper layer so domain never imports SDKs directly. ⚠️ GATED: Only use when ticket explicitly requires adding an external service/SDK that is not previously implemented or integrated in the codebase. Examples: new payment provider, analytics SDK, push notification service. Trigger: "integrate new SDK", "add third party service", "create wrapper"
Stage 3: Coding (Presentation Layer) - Write Pages, BLoCs, and Widgets. Presentation layer handles UI, state coordination, and user interaction with zero business logic. ⚠️ INVOCATION: Only use when the ticket touches the presentation layer (UI, screens, BLoC state management). Trigger: Any of the following phrases exactly as written, without variations: "write UI code", "implement presentation layer", "create page", "create bloc"
Stage 2: Implementation Planning - Decide what to create before writing code. Applies the Digestible PR and Naming & Abstraction rules; checks CoreUI availability. Trigger: "plan implementation" (implementation planning intent), "plan this feature" (ticket-to-file planning intent), "what files do we need for implementation"
Modular PR review for Flutter/Dart changes. Auto-detects which rules apply to each changed file, applies the full rule set in skills/rules/ (referenced by name), and returns a copy-paste-ready markdown PR description + review table. Use when a user asks to review a PR, review a branch, compare branches, or check naming, CoreUI, testing, streams, localization, accessibility, logging, or UI/business separation. Trigger phrases: "review this PR", "review my PR", "review feat/X to main", "check my branch", "code review", "analyze my changes".