feat(factory): plan a reviewable design and vertical slices in Tracer v4 #772
No reviewers
Labels
No labels
backend
bug
chore
duplication
effort:complex
effort:medium
effort:trivial
enhancement
follow-up
frontend
fullstack
priority:high
ready-for-agent
refactor
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dries/ocman!772
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/factory-tracer-v4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
New built-in workflow
ocman/tracer@4, prompt changes only:rationale_markdown(product, architecture, program design: types, signatures, call flow) so approval covers it. Restores the tracer-bullet vertical-slice split that v2 had and v3 dropped. Each task carries the design part it implements, because implementation sessions only see their task.Epics pinned to
@3keep their prompts;@3stays readable throughGetFormulaandcompositionSource.Testing
TestBuiltInFormulaAsksForDesignAndVerticalSlices: fails against the v3 prompts, passes with v4.TestBuiltInFormulaContainsItsPromptsnow checks v3 is not rewritten.go test ./internal/factory/... ./internal/server/... ./internal/mcp/...andgolangci-lint run ./internal/factory/...pass.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.