effective-workflowlisted

# Effective Workflow Coordinate the path from intent to evidence. Let repository instructions and specialist skills own how the work is done; own what should happen next, which authority applies, and what must be true before completion. ## Start from the Host and Repository 1. Inspect the repository instructions, current state, relevant artifacts, and available skills or tools before choosing a workflow. 2. Restate the requested outcome, material constraints, and authorized scope. Infer routine details from local evidence; ask only when a missing choice would materially change the result or authority. 3. Preserve unrelated work and repository-native conventions. Do not create an Effective Workflow config, hidden directory, plan store, label system, role registry, or status marker. 4. Keep analysis-only requests read-only. Treat diagnosis, implementation, and delivery as separate authority levels even when the likely fix is obvious. ## Select the Smallest Route Classify the immediate need before acting: - answer or explain: inspect enough evidence and report without mutation; - diagnose: reproduce or trace the cause, then stop unless a fix is authorized; - plan: use the repository's existing issue, plan, or decision conventions; - build or fix: implement the narrowest authorized behavior change; - refactor: establish a before baseline, preserve behavior, and compare after; - documentation, dependency update, port, architecture, test, or review: hand s