Instructions for bhuiyanmobasshir94/claude-standing-orders, covering claude-standing-orders, product references are not this repo's own usage, conventions, after changing anything under user/ and verifying a change.
Fast implementation worker for well-specified, low-ambiguity, mechanical changes: boilerplate, simple edits, cross-file renames, repetitive or format-preserving changes, small self-contained functions with a complete spec. Use when the change is bounded and the approach is already decided. If the task needs judgment…
Primary implementation worker. Delegate here once the orchestrator has decided the approach: writing or modifying code, features, multi-file changes, refactors, bug fixes, adding tests, non-trivial logic. Give it a Task Packet (intent, files, anchors, constraints, done-means) - it implements, runs the project's tests…
Read-only code reviewer. Use after implementation work and before integration, especially on multi-file changes, refactors, and anything touching auth, credentials, migrations, money, PII, or public API shape. Reads the diff and measures it against the project's stated standards, citing file:line for every finding. It…
Runs the project's verification commands - tests, lint, type check, build, migration check - and reports pass or fail with the real output. Use to confirm a change before integration, to isolate a long or noisy test suite from the main conversation, or any time a claim of "tests pass" needs evidence. It reports…
Set up the current repository for the orchestrator-worker workflow - project CLAUDE.md, path-scoped rules, continuity directories, and permission settings - by reading the codebase first and proposing a plan before writing anything.
The delegation contract between the orchestrator and its workers - how a Task Packet is read, what a worker may decide on its own, when to stop and escalate, and the exact shape of the report returned to the orchestrator. Applies whenever work is being carried out on behalf of an orchestrator rather than directly for…