Starter briefs
Add a field to a form we already have
Name the field, where it should live on an existing form, and get a working save-and-show for it.
The brief
Copy this text as it is, or change the specifics to match your own case, then file it as a task.
Copy this and file it as a task
We already have a form for this, but it's missing one field we need. Add a field for it near the other related fields, let people fill it in and save it, and show the saved value wherever we already show the rest of that form's data. It doesn't need to be required. It just needs to be there, and working.
Why this works
It reuses a form and a data flow that already exist, so the shape of the change is small and known: one new field, one place it saves, one place it shows. Done is easy to check by filling it in and looking for it later.
How it runs
Plan, code, review, merge, verify
- plan
Reads the form's existing fields and the record it saves to, and decides where the new field fits in both.
- code
Adds the field to the form, the place it saves to, and the screen that shows the saved value back.
- review
Checks the new field against the form's existing validation and layout conventions.
- merge
Opens a pull request adding one field and nothing else.
- verify
Confirms the field can be filled in, saved, then shown back correctly.
What you need on hand
- The form the field should join, and where on it
- What kind of value it holds (text, a date, a choice from a list, and so on)
- Where the saved value should show up afterward
Done when
- The field appears on the form where it was asked for
- A saved value shows up wherever the rest of that form's data shows
- Filling in or leaving the field empty both work as expected
Proof, not a promise
No real task in examples.ts matches this brief's exact shape yet. What's real is the mechanism: an agent extends a form and its saved record together, in the same change, so the new field works end to end rather than only on screen.
Keep going
Related briefs
A control that is cut off on a phone
File the button or menu that gets clipped on a narrow screen, and get it fixed.
Bump one dependency and fix what breaks
Name the dependency and the version, and get an upgrade with whatever it breaks already fixed.
One thing has two names; give it one
Name the two terms that mean the same thing, and get the whole codebase moved to one of them.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.