proposelisted

# Align before building Plan a non-trivial change, get it reviewed against simplicity principles, then confirm with the user. Returns an **approved plan** that a downstream skill (or you) can implement. Use this when the work is big enough that you want alignment before writing code. The `feature` skill applies it as Step 1; it can also be applied standalone for a refactor, a bug-fix approach, or a spike design. **Reference files:** - `$HOME/.config/agent-config/hickey-principles.md` — simplicity criteria for the design review --- ## Parse the request Split the text supplied with the invocation into the description and optional `--workspace <name>`. If `--workspace <name>` is provided, fetch the workspace record so the plan targets the right worktree: ```bash node "$HOME/.config/agent-config/lib/workspace.mjs" get <NAME> ``` Use its `worktreePath` as the working directory for the Plan agent. If no workspace, use the current working directory. Also load the project profile so the plan knows the stack: ```bash node "$HOME/.config/agent-config/lib/workspace.mjs" bootstrap node "$HOME/.config/agent-config/lib/project.mjs" load ``` Extract `$STACK`, `$DEPLOY_MODEL`, `$BUILD_CMD`. A `null` command means the project has no such step — take it at face value. --- ## Step 0: Explore from a current tree The Plan agent reads whatever is on disk. A checkout 21 commits behind the remote once led it to plan around a feature that had already shipped — the exploration is only a