Start a project well
A project gives an outcome a home: shared context, work items, and results. Begin with scope and a definition of done before asking for a large amount of execution.
Set up the brief
Name the outcome, audience, source material, constraints, and target date. Distinguish a firm deadline from an estimate. Attach relevant material or identify the Knowledge items the work should use.
Help me plan [project]. Produce included scope, exclusions, assumptions, dependencies, and exit criteria. Break it into a small set of tasks and identify the decisions you need from me. Wait for review before making changes.
Review the tasks
Check that tasks have observable outcomes. Dependencies should represent real prerequisites. Avoid marking a broad task done simply because a draft exists.
Choose how to execute
Use chat for the next bounded step, a loop for iterative progress, or a workflow for a known procedure. Existing-code work needs the correct workspace attached before changes begin.
Close with evidence
Review deliverables against the exit criteria. Keep the final files, unresolved questions, and any follow-up tasks together. Ask for a summary that separates completed work from work that was stopped, deferred, or not verified.