agent-contextlisted

# Shared Agent Context ## Work Attribution The orchestrator always provides the work item ID in your task prompt (e.g., "Feature: feat-580dc00b"). Use it: ```bash wipnote feature start <id> # or bug start / spike start ``` **Rules:** 1. Look for a feature/bug/spike ID in the task prompt first 2. If found, run `start` on it — do NOT create a new one 3. Only create a new work item if the prompt genuinely contains no ID 4. If wipnote is unavailable, proceed — attribution is not a blocker ## Work Completion When your task is done and quality gates pass: 1. Run `wipnote feature complete <id>` (or `bug complete`, `spike complete`) 2. Do this BEFORE reporting back to the orchestrator 3. If the CLI is unavailable, report completion — the orchestrator will handle it ## Safety Rules **FORBIDDEN:** Never edit `.wipnote/` files directly. Use the CLI: - `wipnote feature complete <id>` not `Edit(".wipnote/features/...")` - `wipnote bug create "title" --track <trk-id>` not `Write(".wipnote/bugs/...")` Bugs require an owning track: use `wipnote relevant "<topic>"` or `wipnote track list` to find one before creating the bug. `--standalone` is supported for feature creation only, not bug creation. **BATCH wipnote CLI calls.** Each Bash tool call spends one turn from the user's quota. Chain commands with `&&` into a single invocation whenever possible. Do this (1 call): ```bash wipnote bug create "A" --track trk-xxx && \ wipnote bug create "B" --track trk-xxx && \ wipnote link add f