Draft pull request after ApproveSkill · implement-changeWaits for Approve

Build a website

Build a simple company website in the repository, then open a draft pull request after you Approve.

Layer 01

What you say to StellarFirm

Build a simple website for the company and open a pull request.

Layer 02

What StellarFirm tells the coding session

Build a simple website in the repository the CEO named: a home page, a short about page, and a contact page. Follow the repository's existing UI patterns. Do not add a new stack, a payment step, or a new email vendor.

Keep the Slack text as the task. Add any page or acceptance note the CEO named.

Edit the working tree only. Do not commit, push, merge, or switch away from the current branch.

Run the repository's quality gate from AGENTS.md (for example lint, typecheck, test) and report the commands you ran and their results.

After the CEO Approves, the Coder publishes a new stellarfirm/coder/<slug>-<job> branch with git push -u origin (never force) and opens a draft pull request against the branch the checkout was on.

Never merge from this session. Never force-push. Never push the default branch. Merging and shipping the pull request follow the company's house rules.

Do not use subscription-login tokens. Keep keys, passwords, and personal data out of the prompt.

Back to the Coder library