Build a task-specific plan from reusable workflow steps, then track and adapt the work as it proceeds. It suits requests that span documentation, research, building, or coordination and need a flexible process rather than a fixed workflow.
- Plan and track a mixed set of project tasks
- Adapt the work plan when requirements change
- Coordinate research, implementation, and review steps
griddynamics/rosetta☆ 375Updated Nov 17, 2026
Turn test cases from a test management or issue tracking system into backend API test specifications and automated test files. The workflow checks API details, asks about gaps, and uses user approval gates before implementation and corrections.
- Create API tests from existing test management cases
- Clarify missing or conflicting API requirements
- Review test execution failures and propose corrections
griddynamics/rosetta☆ 375Updated Nov 17, 2026
Use this skill to route test automation requests to a workflow for UI and browser tests, backend API tests, or test case generation from tickets and documents. It directs each request to one specialized flow; mixed or unclear requests need clarification.
- Routing a browser or end-to-end testing request
- Sending API contract tests to the API workflow
- Generating test cases from a Jira ticket
griddynamics/rosetta☆ 375Updated Nov 17, 2026
Organize a workspace after Rosetta setup by choosing a layout, documenting business and technical context, and configuring ecosystem tools. For single-repository workspaces, it can also catalog read-only reference code.
- Choosing a workspace layout
- Documenting business requirements and technical architecture
- Cataloging read-only reference code
griddynamics/rosetta☆ 375Updated Nov 17, 2026
Assess whether a backlog story has enough grounded information for sprint work, separating business readiness from technical feasibility. When work is approved, break it into sequenced packages or a human-readable work breakdown structure.
- Checking a story before sprint intake
- Finding unanswered questions during backlog grooming
- Separating business readiness from technical feasibility
griddynamics/rosetta☆ 375Updated Nov 17, 2026
Keep long-running work aligned with its requirements by creating a persistent, ranked checklist before implementation. Update it as scope changes, then reload it at the end to verify each completion condition against evidence and resolve remaining issues.
- Keeping requirements visible during multi-session work
- Tracking newly discovered constraints and risks
- Verifying completion against evidence
griddynamics/rosetta☆ 375Updated Nov 17, 2026