Skip to content

docs: restructure README around the user journey #238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
omaiesh wants to merge 13 commits into
base: main
Choose a base branch
from
Open

docs: restructure README around the user journey #238

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
01cf34c
docs: restructure README around the user journey
omaiesh Aug 9, 2026
6031816
docs: rewrite README as a shorter, problem-led face
omaiesh Aug 11, 2026
0fdab6d
docs: drop CONFIGURATION.md from this PR
omaiesh Aug 11, 2026
20cfc30
docs: collapse the Documentation section and complete its table
omaiesh Aug 11, 2026
da00fcc
Merge origin/main into docs/readme-user-journey-216
omaiesh Aug 13, 2026
f6599e8
Merge remote-tracking branch 'origin/main' into docs/readme-user-jour…
omaiesh Aug 17, 2026
9f07e29
docs: add skills, workflows, examples, and recommendations to README
omaiesh Aug 17, 2026
95d2292
docs: restructure Set up your repository, trim Documentation table, r…
omaiesh Aug 19, 2026
a589b6c
docs: adopt reviewer-requested structure, ground workflow skills in s…
omaiesh Aug 23, 2026
39ab595
docs: flatten workflow categories, reorder entries, minor skill copy …
omaiesh Aug 23, 2026
0958f09
docs: revert intro to problem-led framing, ground Skills callout in d…
omaiesh Aug 24, 2026
6ea8a30
docs: describe workflow logic in the All-In-One tables
omaiesh Aug 26, 2026
c77e9cd
Merge origin/main into docs/readme-user-journey-216
omaiesh Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs: flatten workflow categories, reorder entries, minor skill copy … 
…fixes

Removes the six category divider headings under All-In-One Workflows after
settling on a size (## then #### then ## again) that kept conflicting with
either the section's own heading or its child ### 4.x entries -- a flat list
matches the reviewer's original template exactly and avoids the ambiguity.

Reorders the 13 entries: Code Analysis and Ad-hoc move up to 4.3/4.4, the QE
cluster (Test Case Generation, API AQA, UI AQA) follows as 4.5-4.7, then
Requirements Authoring at 4.8. Also bumps the skill count callout to "40+".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
  • Loading branch information
@omaiesh @claude
omaiesh and claude committed Aug 23, 2026
commit 39ab595e154a65df66ba7e30a41b12ebb4eb3abb
60 changes: 24 additions & 36 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,6 @@ Connect the agent to your other tools, such as a code graph or test runner. Add

Those are implemented to fully cover entire area of work as All-In-One. If full workflow is not needed you can ask or use skills directly.

**Getting started**

### 4.1 Help Workflow

Finds the right workflow for your request and hands off directly into it.
Expand All @@ -59,8 +57,6 @@ Use it when you do not know what Rosetta can do, or which workflow fits.

[Help Workflow Details](https://griddynamics.github.io/rosetta/docs/help-flow/)

**Coding**

### 4.2 Coding Workflow

Orchestrates subagents and executes: discovery, design, specifications, hitl, implementation, review, unit/integration/e2e testing, final manual validation by AI.
Expand All @@ -71,7 +67,17 @@ Covers E2E and gives a fully implemented and tested solution. Intended for mediu

[Coding Workflow Details](https://griddynamics.github.io/rosetta/docs/coding-flow/)

### 4.3 Ad-hoc Workflow
### 4.3 Code Analysis Workflow

Reverse-engineers a codebase into architecture documentation. Every claim traces to real code.

Use it to understand a system before you plan, refactor, or migrate it.

@isolomatov-gd isolomatov-gd Aug 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is a failure.

Look how example for coding flow was provided and how this one does. First of all lie about architecture documentation (too narrow scoped to architecture documentation also it is NOT ONLY reverse engineering), third sentence repeats what first do (useless tautology).

### 4.2 Coding Workflow

Orchestrates subagents and executes: discovery, design, specifications, hitl, implementation, review, unit/integration/e2e testing, final manual validation by AI. 

Covers E2E and gives fully implemented and tested solution, intended to be used with medium to large tasks. 

[Coding User Guide](user-guide/scenarios/coding.md) · [Coding Workflow Details](https://griddynamics.github.io/rosetta/docs/coding-flow/)


**Skills:** [`/requirements-authoring`](instructions/r3/core/skills/requirements-authoring/SKILL.md), [`/reverse-engineering`](instructions/r3/core/skills/reverse-engineering/SKILL.md), [`/reasoning`](instructions/r3/core/skills/reasoning/SKILL.md), [`/large-workspace-handling`](instructions/r3/core/skills/large-workspace-handling/SKILL.md), [`/questioning`](instructions/r3/core/skills/questioning/SKILL.md)

[Code Analysis Workflow Details](https://griddynamics.github.io/rosetta/docs/code-analysis-flow/)

### 4.4 Ad-hoc Workflow

Builds a custom plan from reusable building blocks, then executes it with tracking.

Expand All @@ -81,9 +87,17 @@ Use it for small or unusual tasks that do not fit any other workflow.

[Ad-hoc Workflow Details](https://griddynamics.github.io/rosetta/docs/adhoc-flow/)

**Quality engineering (QE)**
### 4.5 Test Case Generation Workflow

Turns a ticket into a requirements document and a set of manual test cases.

Use it when you need designed test scenarios with traceability, before any automation code exists.

**Skills:** [`/data-collection`](instructions/r3/core/skills/data-collection/SKILL.md), [`/qa-knowledge`](instructions/r3/core/skills/qa-knowledge/SKILL.md), [`/hitl`](instructions/r3/core/skills/hitl/SKILL.md), [`/coding`](instructions/r3/core/skills/coding/SKILL.md)

### 4.4 API AQA Workflow
[Test Case Generation Workflow Details](https://griddynamics.github.io/rosetta/docs/testgen-flow/)

### 4.6 API AQA Workflow

Turns API contracts and test cases into working, corrected, automated tests. Gated by your approval.

Expand All @@ -93,7 +107,7 @@ Use it to automate backend API tests from OpenAPI specs or request/response case

[API AQA Workflow Details](https://griddynamics.github.io/rosetta/docs/api-aqa-flow/)

### 4.5 UI AQA Workflow
### 4.7 UI AQA Workflow

Turns a test case into a working automated UI test. Follows your repo's existing page objects.

Expand All @@ -103,19 +117,7 @@ Use it to automate browser or end-to-end tests, or to fix a failing one.

[UI AQA Workflow Details](https://griddynamics.github.io/rosetta/docs/ui-aqa-flow/)

### 4.6 Test Case Generation Workflow

Turns a ticket into a requirements document and a set of manual test cases.

Use it when you need designed test scenarios with traceability, before any automation code exists.

**Skills:** [`/data-collection`](instructions/r3/core/skills/data-collection/SKILL.md), [`/qa-knowledge`](instructions/r3/core/skills/qa-knowledge/SKILL.md), [`/hitl`](instructions/r3/core/skills/hitl/SKILL.md), [`/coding`](instructions/r3/core/skills/coding/SKILL.md)

[Test Case Generation Workflow Details](https://griddynamics.github.io/rosetta/docs/testgen-flow/)

**Requirements, specs & research**

### 4.7 Requirements Authoring Workflow
### 4.8 Requirements Authoring Workflow

Drafts and validates requirements as small, atomic units. Each unit needs your approval.

Expand All @@ -125,16 +127,6 @@ Use it when behavior is unclear or high-impact, or when you need traceability.

[Requirements Authoring Workflow Details](https://griddynamics.github.io/rosetta/docs/requirements-authoring-flow/)

### 4.8 Code Analysis Workflow

Reverse-engineers a codebase into architecture documentation. Every claim traces to real code.

Use it to understand a system before you plan, refactor, or migrate it.

**Skills:** [`/requirements-authoring`](instructions/r3/core/skills/requirements-authoring/SKILL.md), [`/reverse-engineering`](instructions/r3/core/skills/reverse-engineering/SKILL.md), [`/reasoning`](instructions/r3/core/skills/reasoning/SKILL.md), [`/large-workspace-handling`](instructions/r3/core/skills/large-workspace-handling/SKILL.md), [`/questioning`](instructions/r3/core/skills/questioning/SKILL.md)

[Code Analysis Workflow Details](https://griddynamics.github.io/rosetta/docs/code-analysis-flow/)

### 4.9 Research Workflow

Drafts a research prompt for your approval, then runs it and documents the answer.
Expand All @@ -145,8 +137,6 @@ Use it for deep investigation or a technology comparison before you choose an ap

[Research Workflow Details](https://griddynamics.github.io/rosetta/docs/research-flow/)

**Modernization**

### 4.10 Modernization Workflow

Migrates or upgrades a system through sequential, spec-first phases. Each phase needs your approval.
Expand All @@ -167,8 +157,6 @@ Use it when your project depends on an internal SDK or external client, without

[External Library Onboarding Workflow Details](https://griddynamics.github.io/rosetta/docs/external-lib-flow/)

**Governance & prompt authoring**

### 4.12 Security Workflow

Runs an authorized security review and prepares remediation inputs. It never fixes code itself.
Expand All @@ -191,7 +179,7 @@ Use it to create, refactor, review, or port a prompt to another agent.

## Skills

40 skills power these workflows. Browse them [here](instructions/r3/core/skills).
40+ skills power these workflows. Browse them [here](instructions/r3/core/skills).

## Documentation

Expand Down