How To Sharpen the Saw

Sustainable velocity requires periodic consolidation. This section shows you how to prompt AI to help maintain quality while moving fast.

Proven by evidence: Projects that consolidated every 10-15 PRs maintained 3-11 PRs/day velocity for weeks. Those that skipped consolidation saw velocity drop by 50% after 20-30 PRs.

The Consolidation Pattern

Every 10-15 feature PRs, have AI help you consolidate.

Real Example: dikuclient PR #15

dikuclient PR #15 was a consolidation checkpoint after PRs #1-14. It:

See dikuclient case study for details on how consolidation enabled higher velocity in subsequent phases.

Every 10-15 feature PRs, pause to consolidate. This isn’t “slowing down”—it’s maintaining the capacity to move fast.

What is a Consolidation PR?

A checkpoint that:

Not: New features, architectural changes, or scope expansion.

The 10-15 PR Rhythm

Why this frequency?

Evidence from projects:

What Consolidation Includes

Based on real case study examples:

See dikuclient PR #15 and DikuMUD PR #122 in the case studies for real consolidation PR examples.

Test Growth from Case Studies

Healthy growth (morpheum example):

Tests grew steadily with features. See morpheum case study for details.

Documentation from Case Studies

dikuclient PR #48: Updated README to reflect current state after 30+ PRs

DikuMUD PR #122: Created comprehensive quest documentation

See the case studies for examples of documentation consolidation PRs.

Technical Debt Management

Not all debt is bad. The key is conscious choice and periodic paydown during consolidation PRs.

The case studies show that projects maintaining a consolidation rhythm every 10-15 PRs sustained higher velocity over time.

Performance and Optimization

Optimize based on evidence, not speculation. Measure before and after, no speculation.

Reflection and Learning

The most important consolidation activity: learning from what happened.

Review the “What Went Well” and “Challenges & Learning” sections in the case studies to see how successful projects captured learnings.

The 10-15 PR Consolidation Rhythm

Based on case study evidence:

Every 10-15 PRs:

Projects maintaining this rhythm sustained 3-11 PRs/day velocity for weeks.

Sustainable Velocity

The goal isn’t maximum speed—it’s sustainable speed.

Case studies show projects maintaining consolidation rhythm achieved:

See velocity metrics in the case studies for detailed analysis.

Sharpen the Saw Checklist

You’re maintaining well when:

Key Finding from Case Studies

Projects that consolidated every 10-15 PRs maintained 3-11 PRs/day velocity for weeks. Those that skipped consolidation saw velocity drop by 50% after 20-30 PRs.

Consolidation is not optional—it’s what enables sustained velocity.

Example: dikuclient Phase 2 Consolidation (PR #15)

Before consolidation (PR #1-14):

After consolidation (PR #16-45):

Investment: 1 consolidation PR enabled 30 faster feature PRs.

See dikuclient case study for full details.

What’s Next?

You’ve completed the journey:

Now: Apply these practices to your projects. Start with Getting Started, progress through each level, and remember—consolidate every 10-15 PRs!

Evidence sources: dikuclient PR #15 (consolidation example), DikuMUD PR #122 (documentation consolidation), morpheum test growth trajectory, velocity metrics from all case studies showing sustainable pace.