griddynamics/rosetta

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

arrange-workspace-flow

Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.

arrange-workspace-flow

Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.

help-flow

Help about Rosetta: explains capabilities and usage.

help-flow

Help about Rosetta: explains capabilities and usage.

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

natural-writing

To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.

design

To decide architecture — alternatives, tradeoffs, committed decision with rationale, boundaries, domain-specific concerns.

discovery

To establish what exists — affected areas, behavior, prior attempts, dependencies, data.

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

design

To decide architecture — alternatives, tradeoffs, committed decision with rationale, boundaries, domain-specific concerns.

discovery

To establish what exists — affected areas, behavior, prior attempts, dependencies, data.

tech-specs

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

dangerous-actions

CRITICAL. MUST activate when action OR its consequence is potentially dangerous/irreversible/destructive, or HIGH RISK — even if it seems safe. If stage, pre-prod, prod envs. Activate even on a remote chance.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

coding-flow

Workflow for all coding: features, fixes, refactors, unit tests, etc.; scales small to large.

external-lib-flow

Workflow for onboarding an external private library so AI can use it without source access.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

coding-flow

Workflow for all coding: features, fixes, refactors, unit tests, etc.; scales small to large.

external-lib-flow

Workflow for onboarding an external private library so AI can use it without source access.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.

requirements-authoring

To author, update, and validate functional/non-functional requirements as atomic units with user approval.