Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

read-ticket

Estrelas2

Forks0

Atualizado23 de junho de 2026 às 08:26

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"

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ripplearc

ripplearc/construculator-app

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

Mais deste repositório

mesmo repositório

code-data

ripplearc/construculator-app

Stage 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)

2026-06-232

code-domain

ripplearc/construculator-app

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"

2026-06-232

code-integration

ripplearc/construculator-app

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"

2026-06-232

code-presentation

ripplearc/construculator-app

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"

2026-06-232

plan-implementation

ripplearc/construculator-app

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"

2026-06-232

pr-review

ripplearc/construculator-app

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".

2026-06-232

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

Read Ticket Skill

Verb: Understand what to build.

Agent's first action when assigned a story. Output primes plan-implementation and subsequent coding skills.

Input

ticket_id: YouTrack ID (e.g., "CA-123")
output_format (optional): structured or conversational

Workflow

Fetch ticket via mcp__youtrack__get_issue(issueId: ticket_id)
- Extract: summary, description, custom fields, comments
- Handle errors: ticket not found, missing description
- Fallback: If YouTrack MCP unavailable, ask user to paste ticket content directly
Identify layers touched (presentation, domain, data, integration)
- UI changes/screens → presentation
- Business logic/rules → domain
- API/DB/cache → data
- New SDK → integration (ask user to confirm)
Anticipate classes (rough scope, not final naming)
- Presentation: {Feature}Page, {Feature}Bloc/Event/State
- Domain: {Verb}{Noun}UseCase, {Noun}Repository (interface)
- Data: Remote/Local{Noun}DataSource, {Noun}RepositoryImpl
Determine test types
- Unit tests: always
- Widget tests: if presentation touched
- Golden tests: if layout-sensitive UI
- Mutation tests: if 4+ conditional branches (per Mutation Testing: skills/rules/13-mutation-testing.md)
- Accessibility tests: if critical flow
Flag ambiguities
- Missing: user flow, edge cases, data source, design refs
- Unclear: acceptance criteria, conflicting requirements
- Surface to developer before plan-implementation
Output analysis
- Layers touched + next skills needed
- Anticipated classes
- Required test types
- Ambiguities + clarifying questions
- Estimated complexity

Output Format

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

References

Next skill: skills/plan-implementation/SKILL.md