Clarify chat-safe property assessor behavior
This commit is contained in:
@@ -65,6 +65,8 @@ Operational rule:
|
||||
- The helper returning a preliminary payload is not the end of the job.
|
||||
- For a user request that clearly asks for a full assessment or PDF delivery, the agent is expected to continue the missing analysis after the helper returns.
|
||||
- Preliminary helper output should be treated as structured scaffolding for the remaining work, not as a reason to stop and wait for another user nudge.
|
||||
- In chat/messaging runs, do not waste the turn on `npm install` or `npm ci` when the local skill dependencies are already present.
|
||||
- If the user asks `update?` or `and?` mid-run, treat that as a status request and continue the same assessment rather than restarting or stopping at the last checkpoint.
|
||||
|
||||
### `assess`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user