# Shrey Junior Commands

This file is generated by Shrey Junior.
Profile: `{{profileName}}`
Detected project type: `{{projectType}}`

Use this file when you need the shortest map of what the control-plane commands do.

Read alongside:
- `.agent/state/active-role-hints.json`
- `.agent/memory/current-focus.json`
- `.agent/context/specialists.md`

## Bootstrap

- `sj-init`: default one-command entrypoint from any folder. Use it when you do not want to decide `bootstrap` versus `standardize` manually. Do not use it when you explicitly need a lower-level dry-run comparison.
- `shrey-junior bootstrap --target <repo>`: install the repo-local contract into an empty or effectively empty folder. Do not use it for an already-lived-in repo unless you intentionally want bootstrap-style initialization.
- `shrey-junior standardize --target <repo>`: selectively upgrade an existing repo or project. Do not use it when repo authority explicitly opts out.

## Implementation

- `shrey-junior status --target <repo>`: read the current repo-local continuity state. Use it before non-trivial work or when resuming. Do not treat it as a substitute for reading the files it points to.
- `shrey-junior run "<goal>" --target <repo>`: generate one focused serious-task packet. Use it for one-owner non-trivial work. Do not use it for trivial edits or explicit multi-role coordination.
- `shrey-junior fanout "<goal>" --target <repo>`: generate planner, implementer, reviewer, and tester packets without a dispatch manifest. Use it when role separation matters but coordination can stay lightweight.
- `shrey-junior dispatch "<goal>" --target <repo>`: generate coordinated multi-role work plus a dispatch manifest. Use it when outputs will be collected and reconciled explicitly.

## QA And Continuity

- `shrey-junior check --target <repo>`: validate repo-local contract, continuity artifacts, and portable state. Use it before medium/high-risk work and before review or push.
- `shrey-junior checkpoint "<milestone>" --target <repo>`: record a git-aware continuity snapshot at a meaningful phase boundary. Use it after coherent work, before handoff, or before push-readiness discussion. Do not use it as a diary entry for every tiny edit.
- `shrey-junior handoff --target <repo> --to-tool <tool>`: create a compact repo-local handoff to another tool. Use it when work is switching from implementation to QA or between Codex, Claude, and Copilot-assisted review. A good handoff should leave `next file`, `next command`, `checkpoint`, and evidence obvious.
- `shrey-junior reconcile --target <repo>`: synthesize multi-role results after collect/dispatch work. Use it before checkpointing or trusting coordinated outputs.

## Release

- `shrey-junior push-check --target <repo>`: assess whether the repo is ready for push discussion. Use it before suggesting push on non-trivial work. Do not treat it as a commit or push command.

## Typical Next Steps

- After `sj-init`: fill `.agent/context/architecture.md`, then record a checkpoint.
- After `run`: open the generated packet, do the work, then checkpoint.
- After `fanout` or `dispatch`: complete role outputs, collect or reconcile, then checkpoint.
- After `checkpoint`: either hand off, continue implementation, or run `push-check`.
