Zephyr Explore
Audit workflow
For every non-trivial task that writes to the workspace, choose a stable task
slug and keep agent-only records under:
.zephyr-skills/<agent-task>/
├── audit.md # Baseline, decisions, evidence, verification, and gaps
├── commands.md # Redacted commands, working directories, and results
├── scripts/ # Intermediate debug documents, scripts, and harnesses
├── output/ # Non-Zephyr dependencies and temporary binaries
└── logs/ # Decisive build, test, runtime, or diagnostic logs
Put every generated intermediate debugging document, debug script, and
scaffolding or harness script, including Bash and Python scripts, under
scripts/, never in a build directory. Put non-Zephyr third-party source or
libraries acquired solely for the agent's task, and temporary binaries produced
by agent-only probes or tools, under output/. Do not copy normal Zephyr build
artifacts there. Keep other agent plans and temporary evidence in the same task
directory. In a Git worktree, add
/.zephyr-skills/ to the repository-local exclude file returned by
git rev-parse --git-path info/exclude before writing audit artifacts. Preserve
existing entries, avoid duplicates, and verify before handoff that
git status --short contains no .zephyr-skills/ paths. Keep Zephyr-native
build trees, binaries, and test outputs separate: honor a user-specified path,
otherwise use defaults such as configured build.dir-fmt, build/, or
twister-out/. Record the effective paths, do not stage .zephyr-skills/
unless requested, and report the task directory and unresolved gaps at handoff.
Investigate
- Bound the question to paths, symbols, configuration, and behavior.
- Search current source, tests, documentation, and
MAINTAINERS.yml before
using history or external material.
- For branch comparisons, use the user-specified target. Otherwise resolve the
configured upstream and use
git merge-base HEAD <upstream>; report a
missing target or upstream instead of guessing.
- Use local history when current source does not explain intent or a
compatibility constraint.
- Consult primary external sources only when local evidence is insufficient.
- Stop when the evidence supports the next design, review, or verification
decision.
Report
- Separate implemented, verified, documented, inferred, and unknown behavior.
- Cite decisive paths, symbols, commits, or external revisions.
- Treat external code as precedent unless import is explicitly in scope and
license-compatible.
1---2name: zephyr-explore3description: Use when Zephyr source, branch history, external precedent, or design constraints must be investigated before a decision can be made.4---56# Zephyr Explore78## Audit workflow910For every non-trivial task that writes to the workspace, choose a stable task11slug and keep agent-only records under:1213```text14.zephyr-skills/<agent-task>/15├── audit.md # Baseline, decisions, evidence, verification, and gaps16├── commands.md # Redacted commands, working directories, and results17├── scripts/ # Intermediate debug documents, scripts, and harnesses18├── output/ # Non-Zephyr dependencies and temporary binaries19└── logs/ # Decisive build, test, runtime, or diagnostic logs20```2122Put every generated intermediate debugging document, debug script, and23scaffolding or harness script, including Bash and Python scripts, under24`scripts/`, never in a build directory. Put non-Zephyr third-party source or25libraries acquired solely for the agent's task, and temporary binaries produced26by agent-only probes or tools, under `output/`. Do not copy normal Zephyr build27artifacts there. Keep other agent plans and temporary evidence in the same task28directory. In a Git worktree, add29`/.zephyr-skills/` to the repository-local exclude file returned by30`git rev-parse --git-path info/exclude` before writing audit artifacts. Preserve31existing entries, avoid duplicates, and verify before handoff that32`git status --short` contains no `.zephyr-skills/` paths. Keep Zephyr-native33build trees, binaries, and test outputs separate: honor a user-specified path,34otherwise use defaults such as configured `build.dir-fmt`, `build/`, or35`twister-out/`. Record the effective paths, do not stage `.zephyr-skills/`36unless requested, and report the task directory and unresolved gaps at handoff.3738## Investigate39401. Bound the question to paths, symbols, configuration, and behavior.412. Search current source, tests, documentation, and `MAINTAINERS.yml` before42 using history or external material.433. For branch comparisons, use the user-specified target. Otherwise resolve the44 configured upstream and use `git merge-base HEAD <upstream>`; report a45 missing target or upstream instead of guessing.464. Use local history when current source does not explain intent or a47 compatibility constraint.485. Consult primary external sources only when local evidence is insufficient.496. Stop when the evidence supports the next design, review, or verification50 decision.5152## Report5354- Separate implemented, verified, documented, inferred, and unknown behavior.55- Cite decisive paths, symbols, commits, or external revisions.56- Treat external code as precedent unless import is explicitly in scope and57 license-compatible.
processmission