docs(how-to): reframe the walkthrough around RoboCo building itself
Recast the how-to as a single thesis: RoboCo is an organization — not a swarm and not a framework — and because it is a real organization (roles, a chain of command, a gated lifecycle, reviews and sign-offs) it can build real software, shown by it building one of its own features. The walkthrough now follows that real feature end to end with screenshots from the actual run: the Board scoping it (Product Owner + Head of Marketing review), the Approve & Start decision, a genuine QA failure and re-run, the three cells' verified, agent-co-authored commits converging, and the integrated pull request — its description, its diff, and the Approve & Merge decision — coming back for the CEO's sign-off, with the final task tree at the end. The human acts at only the two ends; the organization fills in everything between. Adds the new walkthrough screenshots and places them across the lifecycle.
Renn F
|
After Width: | Height: | Size: 255 KiB |
|
After Width: | Height: | Size: 313 KiB |
|
Before Width: | Height: | Size: 162 KiB After Width: | Height: | Size: 94 KiB |
|
After Width: | Height: | Size: 162 KiB |
|
After Width: | Height: | Size: 154 KiB |
|
After Width: | Height: | Size: 412 KiB |
|
After Width: | Height: | Size: 367 KiB |
|
After Width: | Height: | Size: 394 KiB |
|
After Width: | Height: | Size: 318 KiB |
|
After Width: | Height: | Size: 304 KiB |