Schedule
Research + planning + implementing
☕ break
Implementing + PR + merge
Tips + friday demo
About me
20 years — full-stack, mobile, game
214 PRs in 2025 → 415 in 2026
Our focus
Research → Plan → Implement
Approach the discussion with ideas and questions
Use research to construct a detailed phase-based implementation plan
Implement each phase, with tests + commits between
Coding harnesses
Claude code
Skills
MCP tools
Research
Read-only codebase exploration
Write the findings down
Storage options — database, obsidian, markdown
Loop for improvements
Research output isn't always good enough on the first pass
Would you feel confident planning from this?
Questions about research?
New feature
One command → branch + worktree + feature doc
Switch to worktree
Plan
The plan is a written artifact
Each phase gets its own research pass before steps are written
Manual review
Bad plan → bad code, confidently
Check phase order, correctness, completeness
Questions about planning?
Implement
One phase at a time, one sub-agent per phase
Each phase ends with a commit
Phase N: ... commit messages make history readable as a story
☕ Break
Pull request
Pull request description generated from the feature doc
CI watched automatically
Review
Self-healing loop
Phase 1: code quality
Phase 2: blast radius
Final report posted as PR comment
QA checklist
Generated from the feature doc
User-facing only — every item is actionable
Merge
Merge PR → delete worktree → pull main → fix symlinks
Tips & tricks
The AI doesn't remember anything between sessions by default
Commit preferences to a store + amend the system prompt to always search it
pclaude alias
Friday's implementation: SQLite + MCP tool
Let me show you Friday
Questions?
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.