Build Vertical Slice
Make one real user path work from edge to persistence and back before broadening the implementation.
Workflow
- Read the acceptance example and locate the closest end-user entry point.
- Reproduce the missing behavior end to end. Record the exact command or interaction and observed failure.
- Add an acceptance or integration test that fails for the intended reason.
- Add focused unit or contract tests for complex logic and boundary behavior.
- Implement the smallest coherent path through UI or API, domain logic, data, and external boundaries.
- Run the new test, then relevant local suites, lint, type checks, build, and security or accessibility checks.
- Exercise the end-user path again. Capture screenshots or traces for visual behavior.
- Review the diff for unrelated changes, dead scaffolding, debugging output, migration safety, and rollback.
TDD evidence
Preserve:
acceptance_example: spec reference
red:
command: exact command
result: expected failing assertion or observed behavior
green:
command: exact command
result: passing output
refactor:
change: simplification or none
verification: exact command and result
If a failing test cannot be created first, explain why and capture the closest reliable reproduction. Never fabricate a red phase after implementation.
Engineering rules
- Follow repository instructions and existing patterns unless evidence supports changing them.
- Prefer real boundaries; label fakes, mocks, stubs, and skipped integrations.
- Keep the slice narrow, but include its error, authorization, accessibility, observability, and migration obligations.
- Do not weaken assertions, disable checks, or update snapshots merely to obtain green.
- Fix directly related flaky, lint, or test failures rather than hiding them.
Evidence packet
Lead with the user-visible outcome. List files changed, red-green-refactor evidence, end-to-end verification, full relevant checks, visual artifacts, and untested paths. Do not claim completion when the acceptance example remains unexercised.
1---2name: build-vertical-slice3description: Implement the smallest end-to-end user-visible behavior using test-driven development and real system boundaries, then return reproducible acceptance evidence. Use after a spec identifies a concrete slice. Do not use for planning-only or review-only work.4license: Apache-2.05---67# Build Vertical Slice89Make one real user path work from edge to persistence and back before broadening the implementation.1011## Workflow12131. Read the acceptance example and locate the closest end-user entry point.142. Reproduce the missing behavior end to end. Record the exact command or interaction and observed failure.153. Add an acceptance or integration test that fails for the intended reason.164. Add focused unit or contract tests for complex logic and boundary behavior.175. Implement the smallest coherent path through UI or API, domain logic, data, and external boundaries.186. Run the new test, then relevant local suites, lint, type checks, build, and security or accessibility checks.197. Exercise the end-user path again. Capture screenshots or traces for visual behavior.208. Review the diff for unrelated changes, dead scaffolding, debugging output, migration safety, and rollback.2122## TDD evidence2324Preserve:2526```yaml27acceptance_example: spec reference28red:29 command: exact command30 result: expected failing assertion or observed behavior31green:32 command: exact command33 result: passing output34refactor:35 change: simplification or none36 verification: exact command and result37```3839If a failing test cannot be created first, explain why and capture the closest reliable reproduction. Never fabricate a red phase after implementation.4041## Engineering rules4243- Follow repository instructions and existing patterns unless evidence supports changing them.44- Prefer real boundaries; label fakes, mocks, stubs, and skipped integrations.45- Keep the slice narrow, but include its error, authorization, accessibility, observability, and migration obligations.46- Do not weaken assertions, disable checks, or update snapshots merely to obtain green.47- Fix directly related flaky, lint, or test failures rather than hiding them.4849## Evidence packet5051Lead with the user-visible outcome. List files changed, red-green-refactor evidence, end-to-end verification, full relevant checks, visual artifacts, and untested paths. Do not claim completion when the acceptance example remains unexercised.
leihuang23