Revise README for improved clarity on Pstack features

README.md

@@ -2,9 +2,9 @@
 
 **Stop bad code before your agents ship it.**
 
-Pstack helps you build a repo where agents must prove a change works before it can merge. `poteto-mode` gives them the engineering process; a repo-specific verification skill checks real features. Your codebase, static checks, CI, and merge rules make the requirements enforceable. When you catch a mistake, turn it into a check or constraint that prevents it from recurring.
+Pstack helps you build a repo where agents follow the engineering practices you’d expect from a human teammate: understand the codebase, investigate problems, make deliberate design choices, review changes, and verify that they work. `poteto-mode` coordinates that process, and a repo-specific verification skill gives agents a way to test real features. That lets you move faster and run more work in parallel without supervising every step.
 
-Pstack is a collection of **skills with distinct responsibilities**. `poteto-mode` is the entry point: it selects the skills a task needs and coordinates subagents for work such as code exploration (`how`), design (`architect`), implementation, and adversarial review (`interrogate`). Unlike Cursor’s original Pstack, which is limited to models available through Cursor, Open Pstack lets you [assign providers and models by role](#1-set-up-the-models) using your own provider subscriptions—so exploration, implementation, and review can each use a different provider and model.
+Unlike Cursor’s original Pstack, which is limited to models available through Cursor, Open Pstack lets you [assign providers and models by role](#1-set-up-the-models) using your own provider subscriptions—so exploration, implementation, and review can each use a different provider and model.
 
 ```mermaid
 flowchart LR