Workflow Practices

The flows and roles of agent work in this repository: clarifying the request, what an agent may do alone, how a task runs, and when it is done.

Always

• Ask before building when the answer changes what gets built (architecture, business rules, formats, security or data loss, unbounded scope); otherwise state the assumption and proceed. Ask everything in one message, 2 to 4 options, recommended first; never ask what the code, skills or linters decide. A plan, spec or backlog item with many open decisions: offer the enrichment skill
• Read the code, write a todo list, check a behavior-changing plan with the user, then execute
• One package per task, and only what the task needs; a cross-package change follows the protocol; refactors go in their own commit
• Never commit, push, tag, reset, stash, check out, restore or run release commands unless the user asks for that exact action; commit messages carry no AI attribution or session ids
• Never revert what the user changed; undo your own edits with edits
• Ask first before new dependencies, workflow changes, @eserstack/standards changes, publishing config or anything a release cannot undo
• Never edit versions, generated deno.json files or lock files by hand
• Bug fixes: root cause with file:line, failing test first, fix at the origin
• Implement everything asked; TODOs only with a backlog task id
• Done means deno task cli ok passed (make ok is Go only); report what was verified and what was skipped
• Reviewers change nothing, cite file:line and mark each finding blocking or informational
• Everything written into the repo is English, whatever the conversation language

References