feat: add benchmark-driven workflow for performance issues#158
Merged
LeeCampbell merged 2 commits intoHdrHistogram:mainfrom Mar 22, 2026
Merged
Conversation
Establishes a benchmark-first methodology in testing standards and updates autonomous agent prompts to enforce Phase 1 (baseline) → Phase 2 (implement) → Phase 3 (validate) ordering for performance issues, ensuring baseline measurements exist before any code changes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
LeeCampbell
force-pushed
the
feat/benchmark-driven-workflow
branch
from
d857240 to
a0ffab7
Compare
- Remove stale Program.cs from git add in execute-tasks.md - Clarify --job short is only for Phase 2; Phase 1 and 3 use defaults - Add trailing newlines to create-tasks.md and execute-tasks.md - Replace static benchmarks table with directory lookup directive Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
spec/tech-standards/testing-standards.mdwith a comprehensive benchmark-driven development methodology (Phase 1 baseline → Phase 2 implement → Phase 3 validate)pick-issue,review-brief,create-tasks,execute-tasks) to classify issues asfunctionalorperformanceand enforce benchmark-first task orderingagent-loop.shTest plan
spec/tech-standards/testing-standards.mdrenders correctly and covers framework details, 3-phase process, design guidelines, and running instructions./scripts/run.sh 141against a performance issueCategory: performanceandBenchmark strategyfieldsplan/benchmarks/baseline.mdis populated before any implementation changesplan/benchmarks/comparison.mdexists after implementation and appears in PR body🤖 Generated with Claude Code