Developer FAQ

Build approved features.

Fix agreed bugs.

Maintain technical quality and stability.

If something does not work as originally agreed or described, it is a bug and should be fixed without charging as a new feature.

Any new feature, redesign, or scope change beyond the original agreement.

Pause implementation.

Ask for re-estimation through the agent.

Continue only after updated approval.

First the developer marks it done.

Then the agent verifies it.

Finally the client approves it.

Yes, but each request keeps its own queue position, estimate, and priority.

Not while we are responsible for the project.

If needed, collaboration can happen through pull requests.

Projects may be hosted on GitHub Pages or another provider chosen for the client.

Yes. Each project is independent and can be transferred according to the agreement.

Prefer client content when available.

If missing, use generated basic starter content for launch.

Client controls business decisions.

Agent controls communication and validation.

Developer controls technical implementation decisions.

Report it early through the agent.

The timeline should be adjusted or the request re-estimated.

No.

Scope, pricing, and validation should go through the agent workflow.

The feature should be working, reviewed by the developer, and ready for agent verification.

Only if they are clearly beneficial, low-risk, and do not change the agreed scope.

Otherwise they should be proposed first.