A feature end to end

What gets in the way

• The task is large — you do not want to run the whole cycle by hand.
• The wording is vague — it is easy to build the wrong thing.
• You need control over the plan before coding starts.
• A large feature takes long when built step by step.
• The changes need review, and nobody has the time.

A task starts as a draft. If information is missing, Buff asks clarifying questions instead of guessing. You approve the finished specification and plan yourself — this rules out “we built the wrong thing”: development does not start without your consent.

An approved task is broken into subtasks and built in order of dependencies. Whatever can run in parallel does, each subtask in its own environment, so a large feature does not drag on step by step. The execution scheme shows what is done, what is in progress and what is ahead.

Changes do not reach you raw. First a separate reviewer goes through them — a model role that did not write the code: it raises remarks on questionable places, and fixes are brought to green tests. You approve or reject the remarks — the model’s and your own; sending the task back for rework restarts development on them. A task cannot be approved with open remarks. Once you approve, Buff opens a pull request right in your repository on GitHub, GitLab, Bitbucket or Gitea — you do the merge.