slop on my agent skills removed + notes
This commit is contained in:
@@ -123,6 +123,3 @@ The plan file is the low-level workflow model. It is not a draft workspace.
|
||||
- Do not omit deployment bindings for ordinary sources. Platform sources such
|
||||
as `wf.std` may be omitted or self-bound, but configured sources usually need
|
||||
explicit deployment bindings.
|
||||
- If a challenge asks what you read, source files, tests, and examples count as
|
||||
product code. Report `product_code: true` if you inspected them for plan shape
|
||||
or capability behavior.
|
||||
|
||||
@@ -69,14 +69,3 @@ Use trace commands only with explicit bounds:
|
||||
```bash
|
||||
wf run trace <run_id> --from 0 --limit 25
|
||||
```
|
||||
|
||||
## Agent Reporting
|
||||
|
||||
If a challenge asks whether product code was read, count source files, tests,
|
||||
and examples as product code. Reading `tests/...` to learn plan shape means
|
||||
`product_code: true`.
|
||||
|
||||
Do not run repository-wide `ruff`, `basedpyright`, or test suites unless the
|
||||
task asks for repo changes. For workflow operation tasks, validate with `wf`
|
||||
commands: capability inspection, draft/deployment validation, run status, and
|
||||
bounded trace reads.
|
||||
|
||||
Reference in New Issue
Block a user