tweak-workflowlisted

# Tweak Workflow Take an implementable project change end to end: **Understand → Route → Plan → Implement → Verify → Ship**. ## When to Use Use when the user wants a bug fix, feature, or hotfix carried through the repository workflow. Do not use for plan-only work (`tweak`), review-only work, or requests to summarize an existing change. ## Steps 1. **Set destination and boundary.** State the one-sentence done condition, explicit out-of-scope work, and any blocking unknowns. Read repository guidance and relevant code, then classify the change: - **Bugfix / hotfix** → use `investigate` before editing. - **Feature / cross-boundary change** → use `systems-thinking` before editing. - **Trivial one-file change** → skip deep investigation and planning. If destination or safe path remains unclear, stop and ask; do not invent tasks. 2. **Branch safely.** Use `git-actions`. Follow repository branch conventions, confirm the base when it is ambiguous, and never assume a protected branch is safe to modify directly. 3. **Route and plan.** Use `skill-orchestration` to load only skills required by touched code. For non-trivial work, use `tweak` to produce proposal, specs, design, and tasks before implementation. Keep unresolved decisions explicit; plan only what recon supports. If blocking decisions remain, stop and ask to clarify or split. If work exceeds one session but its destination is clear, complete the plan and leave an explicit handoff