Build a feature
Follow ~/agent-skills/working-agreements/AGENTS.md throughout (scope, verification, no push).
Size it first
- Small (one file or component, clear intent): read the neighbors, implement, add or
update a test, run the
verifyskill. No brief. - Medium (several files, some unknowns): write the brief from
workflows/spec.md, state assumptions in one line, implement P0 then P1 without waiting unless something is destructive. - Large (new subsystem, many files, or the user asked for a spec): write the brief with
workflows/spec.md, show it and stop for approval. After approval, split independent parts and hand isolated ones out with thecoordinate-agentsskill: UI parts to Codex, simple parts to Antigravity, the complex core stays with you (~/agent-skills/shared/agent-routing.md).
Steps
- Ground it. Find where the feature lives and what it must match: the closest existing
feature, data model, tests, design system. Use
understand-codeif the area is unfamiliar. - Brief (medium/large) with P0/P1, out of scope, constraints and "done when".
- Implement by extending what exists. No new dependencies or paid APIs without approval.
API work: validate inputs, typed errors, and a test per endpoint. UI work: both themes,
reduced motion, the owner's UI bar (
revamp-uifor big visual changes). - Test the new behavior through production code paths (
test-everythingfor strategy). - Verify on the real target with the
verifyskill, with evidence. - Review large or risky diffs with
review-codeand fix what is confirmed. - Report in 2–5 sentences: what works, how it was verified, what's left.