forked from retoor/devplacepy
docs: document agent isolation and result caching in maintenance docs
- Add explanation that each agent runs in isolation, preventing accidental cascading triggers - Clarify that Maestro runs each agent once and caches results for follow-up questions - Update style agent description to note context-aware application of project rules - Wrap leaderboard test page/browser context in try/finally to ensure cleanup on failure
This commit is contained in:
@@ -25,6 +25,12 @@ with copy-paste commands.
|
||||
build is broken.
|
||||
- Every run writes a small **report** (a JSON file and a readable summary) so you
|
||||
can see exactly what was found and fixed.
|
||||
- Each agent runs **in isolation**: it only ever uses its own reviewing tools, so
|
||||
one agent can never trigger another or kick off the whole fleet by accident. Runs
|
||||
stay fast and predictable.
|
||||
- When you ask Maestro to review **everything**, it runs each agent **once** and
|
||||
remembers the results to answer your follow-up questions, instead of repeating the
|
||||
same work.
|
||||
|
||||
## Meet the fleet
|
||||
|
||||
@@ -37,7 +43,7 @@ with copy-paste commands.
|
||||
| **Docs** | CLAUDE.md, AGENTS.md, README, and these docs pages stay in step with the code, shown to the right audience. |
|
||||
| **Feature completeness** | A new feature is wired all the way through: form, JSON schema, Devii tool, API docs, SEO, and README. |
|
||||
| **Duplication** | Shared helpers are reused instead of copy-pasted logic. |
|
||||
| **Style** | Naming, headers, typing, and formatting follow the project rules. |
|
||||
| **Style** | Naming, headers, typing, and formatting follow the project rules, applied with context so code that intentionally uses a pattern or character is left alone. |
|
||||
| **Frontend** | JavaScript modules, web components, and CSS follow the project's strict structure. |
|
||||
| **SEO** | Public pages carry the right search metadata and appear in the sitemap. |
|
||||
| **Tests** | Routes without an integration test get one written (the agent never runs the suite itself). |
|
||||
|
||||
@@ -30,7 +30,9 @@ python -m agents.maestro "is my documentation up to date?"
|
||||
```
|
||||
|
||||
Maestro defaults to **check** (read-only) for questions and confirms with you
|
||||
before it makes any change.
|
||||
before it makes any change. When you ask it to review the whole project, it runs
|
||||
each agent **once** and reuses those results to answer anything you ask next, so it
|
||||
never repeats the same sweep to look something up.
|
||||
|
||||
## Running one agent yourself
|
||||
|
||||
|
||||
Reference in New Issue
Block a user